Skip to main content
Glama

get_page_structured_data

Returns the curated JSON-LD structured data graphs (Service, SoftwareApplication, Product, Offer, Review, FAQ, Breadcrumb…) for a Siigo landing page, plus SEO metadata. Use this when the user asks about a specific Siigo product or topic and you want canonical, schema.org-ready data. Example call: {"country": "COL", "slug": "facturacion-electronica"}. Pages with no JSON-LD still return title + seo with an empty jsonLdGraphs array.

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": {
      "country": "<country>",
      "slug": "<slug>"
    },
    "name": "get_page_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesWordPress page slug, without leading slash. Lowercase letters, digits and hyphens only, max 200 chars. Real COL slugs: facturacion-electronica, nomina-electronica, software-contable, gestion-de-inventario, sistema-de-costos, gestion-de-cobranza, precios-siigo, por-que-siigo, prueba-gratis. An unknown slug returns 'Page not found'.
countryYesISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU."New value: +"ISO 3166-1 alpha-3 country code. Only countries listed in DependencyInjection:ProfileInjector:Actives are served. Examples: COL, MEX, ECU, PER, CHL, URY."
    • changedInput schema / properties / country / examples
      Previous value: -[
      -  "COL",
      -  "MEX",
      -  "ECU"
      -]New value: +[
      +  "COL",
      +  "MEX",
      +  "ECU",
      +  "PER",
      +  "CHL",
      +  "URY"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does real work: it discloses the return payload shape (jsonLdGraphs plus seo), that JSON-LD-less pages still return title + seo with an empty array, and that an unknown slug yields 'Page not found'. It does not mention auth, rate limits, or whether country availability varies by environment beyond the schema note, but the edge-case behavior is well covered for a read-only fetch.

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?

Three sentences, front-loaded with the return payload, then the usage trigger, then the concrete call example and edge case. Nothing is redundant with the title (which is absent) and every sentence contributes, though the inline example call is partially duplicative of the schema examples.

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?

With only two fully documented parameters and no output schema, the description steps in to sketch the response (JSON-LD graphs, SEO metadata, empty array fallback) and the not-found case. That is close to complete; the only shortfall is not describing what fields 'seo' contains, which matters because no output schema exists.

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%, so the schema already documents both the slug pattern/examples and the ISO alpha-3 country code constraint. The example call {"country": "COL", "slug": "facturacion-electronica"} adds a little concreteness but no meaning beyond what the parameter descriptions and examples already say; baseline 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?

States a specific verb and resource: 'Returns the curated JSON-LD structured data graphs ... for a Siigo landing page, plus SEO metadata', and enumerates the graph types (Service, SoftwareApplication, Product, Offer, Review, FAQ, Breadcrumb). It is clearly distinguishable from generic siblings like search, though it never names get_products as the alternative for non-SEO product lookups.

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?

Gives an explicit trigger: 'Use this when the user asks about a specific Siigo product or topic and you want canonical, schema.org-ready data.' That is a clear usage context, but there are no exclusions or named alternatives even though get_products and search sit right next to it, so the agent must infer when *not* to call this.

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.

Resources