AutoRank MCP

generate_breadcrumb_schema

Generate BreadcrumbList JSON-LD for SEO. Input breadcrumb items with name and URL to produce the structured data.

Instructions

Generate BreadcrumbList JSON-LD. Each item needs 'name' and 'url'.

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": {
      "items": "<items>"
    },
    "name": "generate_breadcrumb_schema"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the generation behavior and the item requirement ('name' and 'url'), but lacks details about return format, side effects, or validation. Since generation is a non-destructive read-like operation, the missing details are not critical, but more clarity would be beneficial.

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

Conciseness5/5

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

The description is two sentences with zero redundancy. Every word contributes to understanding the tool's function and key requirement, exemplifying optimal conciseness.

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?

The tool is simple with one parameter, and the output schema covers return values. The description provides the critical input requirement, making it sufficient for basic invocation. However, it omits broader context like common breadcrumb ordering or when to use breadcrumbs, but that is not essential for a straightforward generator.

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

Parameters4/5

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

The input schema only specifies an array of objects with additionalProperties true, providing no property details. The description fills the gap by stating 'Each item needs 'name' and 'url'', which is essential for correct invocation, thus adding significant meaning beyond the schema.

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 clearly states 'Generate BreadcrumbList JSON-LD', specifying the exact output format and distinguishing it from sibling schema generators like FAQ or Article schema. The additional note about item requirements reinforces the purpose.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as generate_faq_schema or generate_article_schema. It only describes the action and a constraint, leaving the agent to infer appropriate use cases.

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

Deploy Server