Better Fetch

Open Graph Extractor

Retrieve a rendered page and extract Open Graph, Twitter Card, canonical, and standard metadata into reusable records.

Content extractionv0.1.0~1 credit/runSource on GitHub

Workspace

Configure

Inputs stay here while results become exportable artifacts.

Start from an example

Page URL to inspect.

Sign in and run
~1 credit/run10 runs/minute

Results

Preview, inspect, copy, or export the complete output.

Your result will become an artifact

Run the tool to inspect structured rows, raw JSON, execution details, and downloadable JSON, CSV, and Markdown files.

countpropertiessource_url

Overview

Retrieve a rendered page and extract Open Graph, Twitter Card, canonical, and standard metadata into reusable records. This first-party Better Fetch tool turns a focused request into predictable structured output that can be inspected in the web workspace, exported as JSON or CSV, called through REST, or composed by an AI agent over MCP. It is designed for repeatable production research rather than fragile copy-and-paste scraping.

Last validated: Jul 13, 2026

Input

urlstring (uri)required

Page URL to inspect.

Output

countintegerrequired

Number of records returned

propertiesobject[]required

Normalized properties records

source_urlstringrequired

Fetched source URL

Examples

first-run

{
  "url": "https://www.hardgraft.com/products/onepack-coal"
}

Use cases

Agent research

Give AI agents bounded, normalized open graph extractor results without writing source-specific retrieval and parsing code.

Repeatable monitoring

Save the configuration, rerun it on a consistent source, and export comparable structured artifacts for operational review.

FAQ

What does Open Graph Extractor return?

It returns normalized structured fields documented in the output schema, plus the fetched source URL and a record count for receipts and exports.

Does this tool store the retrieved output?

No. Better Fetch records privacy-safe run metadata for reliability and retention analysis, but the output payload itself is not stored by the workspace.

Use it anywhere

MCP (Claude, ChatGPT, Codex)

# After connecting https://betterfetch.co/api/mcp, ask your AI to:
1. Call search_tools for "Open Graph Extractor"
2. Call run_tool with:
   name: "open_graph_extractor"
   input: {"url":"https://www.hardgraft.com/products/onepack-coal"}

REST

curl -sS -X POST "https://betterfetch.co/api/tools/open_graph_extractor/run" \
  -H "Authorization: Bearer bf_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"input": {"url":"https://www.hardgraft.com/products/onepack-coal"}}'

Run locally

git clone https://github.com/better-fetch/tools/tree/main/tools/open-graph-extractor && cd open-graph-extractor && npm i
BETTER_FETCH_API_KEY=bf_your_key_here npx bf-tool run --input '{"url":"https://www.hardgraft.com/products/onepack-coal"}'