seo-geo-mcp-server

Social Preview (Open Graph & Twitter Card) Check

social_preview_check

Read-onlyIdempotent

Diagnose broken social link previews by validating Open Graph and Twitter Card tags. Verifies og:image loads and flags relative URLs that social scrapers reject.

Instructions

Validate the tags that build link-preview cards on X, LinkedIn, Facebook, Slack, WhatsApp and Discord: og:title, og:description, og:image, og:url, og:type, og:site_name and the twitter:* family. Optionally verifies the preview image actually loads, and flags the classic bug of a relative og:image URL (social scrapers require absolute URLs).

Args:

url (string): the page to check.
check_image (boolean): verify the og:image resolves (default true).
response_format ('markdown' | 'json'): output format (default 'markdown').

Returns: { open_graph{}, twitter{}, og_image_url, og_image_reachable, og_image_status, score, grade, findings[] }.

Example: "Why does my link preview look broken on LinkedIn?" -> social_preview_check(url="https://example.com/post").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Page URL to analyse, e.g. 'https://example.com/blog/post'. The scheme defaults to https://.
`check_image`	No	Issue a HEAD request to confirm the og:image actually loads.
`response_format`	No	Output format: 'markdown' for a human-readable summary (default) or 'json' for the full structured payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`grade`	Yes
`score`	Yes
`twitter`	Yes
`findings`	Yes
`final_url`	Yes
`open_graph`	Yes
`og_image_url`	Yes
`og_image_status`	Yes
`og_image_reachable`	Yes
`og_image_content_type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.2.0Sep 16, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / open_graph / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / twitter / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv1.0.0Aug 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, non-destructive). The description adds genuinely useful behavioral context beyond that: it discloses that the tool optionally issues a HEAD request to verify the og:image loads, and that it specifically flags relative og:image URLs — a classic pitfall behavior an agent wouldn't infer from annotations alone.

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?

The description is well-structured: purpose is front-loaded in the first sentence with platforms and tag families, followed by behavioral specifics, then Args/Returns/Example sections. The Args section is somewhat redundant with the fully-covered schema, which prevents a 5, but every other sentence earns its place and the example is tightly scoped.

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

Completeness4/5

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

For a single-URL validation tool with 3 well-documented params, rich annotations, and an output schema, the description is complete: it explains the return payload shape, provides an example, and covers the main behavioral nuance (image reachability check). Nothing essential for correct invocation is missing.

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 coverage is 100%, so the baseline is 3. The description's Args section largely restates what the schema already documents (defaults for check_image and response_format are duplicated). The example does demonstrate realistic invocation syntax, but the description adds minimal semantic value beyond the schema's parameter descriptions.

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?

The description names a specific verb-resource pair ('Validate the tags that build link-preview cards') and enumerates the exact tag families (og:title, og:description, og:image, og:url, og:type, og:site_name, twitter:*) as well as the target platforms (X, LinkedIn, Facebook, Slack, WhatsApp, Discord). This clearly distinguishes it from siblings like meta_tags_check (generic meta tags), image_seo_check, and render_check.

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 example query ('Why does my link preview look broken on LinkedIn?') provides a concrete, actionable when-to-use signal that an agent can match against a user's intent. However, it does not explicitly name alternatives or state when NOT to use this tool (e.g., versus meta_tags_check for general tag validation), so it stops short of full exclusion guidance.

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

Deploy Server