Skip to main content
Glama

ApexSEO GEO & AI-Crawler Audit MCP

JSON-LD & AI Citation Entity Check ($0.01)

schema_citation_check
Read-onlyIdempotent

Extracts and validates all embedded application/ld+json blocks (including @graph trees) on a live page, flags syntax errors and missing AI-citation properties for Organization, WebSite, SoftwareApplication, Product, Article, FAQPage, and WebPage entities, scores schema completeness (0-100), and outputs a ready-to-paste JSON-LD @graph patch customized from detected metadata.

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": "schema_citation_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTPS/HTTP URL to audit live (e.g. https://example.com).

Output Schema

NameRequiredDescriptionDefault
finalUrlYes
parseErrorsNo
schemaScoreYes
detectedTypesYes
iceActionPlanNo
jsonLdBlockCountNo
citationReadinessNo
recommendedJsonLdPatchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real substance beyond that: it discloses multi-stage behavior (parse, syntax-error flagging, missing-property checks per entity type, a 0-100 completeness score) and that the output is a ready-to-paste patch rather than an applied change. It omits operational details such as behavior on pages with no JSON-LD or pages behind auth/bot protection.

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?

Every clause carries information — entity list, @graph handling, scoring range, output artifact — with no filler or repetition. The cost is structural: it is one very long run-on sentence, so the scoring and patch-output facts are buried at the tail rather than front-loaded.

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-parameter audit tool with an output schema, the description covers what is fetched, what is checked, and what is returned (score plus a paste-ready @graph patch), so return-value explanation is not needed. Remaining gaps are edge-case handling for pages without JSON-LD and the absence of the $0.01 cost mention that appears only in the title.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself documenting the HTTPS/HTTP public URL requirement and giving an example. The description adds no further constraint on the parameter (e.g., whether redirects or non-HTML responses are handled), so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb chain (extracts, validates, flags, scores, outputs) against a specific resource (embedded application/ld+json blocks, including @graph trees, on a live page), plus the exact entity types checked. An agent knows precisely what the tool produces. It stops short of naming any sibling, so differentiation from ai_crawler_audit or geo_page_audit relies on the name/title alone.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the 'live page' and structured-data focus make it clear this is for auditing a URL's JSON-LD, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling such as a broader page audit. An agent must infer routing from the tool name and the list of supported entity types.

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.