Skip to main content
Glama

Get the social preview image of a page (what shows when a link is shared)

og_image
Read-only

Get the social preview image of a page (what shows when a link is shared): og:image and twitter:image with declared size and alt text, or the first large page image as a fallback. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.001 per call (x402, USDC on Base).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "og_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful behavioral detail beyond them: the fallback to the first large page image, a sub-2-second latency bound, a 20 calls/day free quota, and the pay-per-call path. However, it omits what happens when no image is found at all and how partial results are reported, which is the main remaining behavioral unknown for a no-output-schema tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and fallback semantics, followed by compact operational facts (speed, quota, price) in two short sentences. Dense and waste-free, though the pricing detail is borderline for a tool description and duplicates the payment parameter's schema text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does it well: it names the fields returned (image URL sources, declared size, alt text) and the fallback source. Combined with latency, quota, and payment context, an agent has everything needed to call this correctly and to anticipate the cost model.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already explains both url and the x402 payment signature flow thoroughly. The description reinforces the payment model ('$0.001 per call, x402, USDC on Base') but adds no new meaning about parameter format or validation, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the social preview image of a page'), then immediately disambiguates scope by naming the exact sources read (og:image, twitter:image) and the fallback strategy (first large page image). This lets an agent distinguish it from siblings like images, meta, favicon, or screenshot without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical 'what shows when a link is shared' gives an unambiguous use context, and the pricing/rate-limit sentences tell the agent when calling is practical. It stops short of naming alternatives or exclusions (e.g. 'use images for all page images, use screenshot for a rendered capture'), so it lands at 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.