Crawlora MCP

yahoo_autos_article

Read-only

Fetch a Yahoo Autos article's full content from a canonical autos.yahoo.com url, including title, summary, author, dates, section, image, keywords, original publisher, and body paragraphs. Use yahoo_autos_home or yahoo_autos_category to discover story links.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical autos.yahoo.com article URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / url / description
```
Added value: +"Canonical autos.yahoo.com article URL"
```
First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the output schema documents the returned fields. The description adds the framing of 'full content' retrieval and the canonical-domain constraint, but no auth, rate-limit, or failure behavior. Adds modest value over structured data.

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?

Two sentences, front-loaded with the action and scope, followed by routing guidance. No filler; every clause earns its place.

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 read-only fetch, the description covers what it does, where to get the input, and what comes back, while annotations and the output schema carry safety and return details. Only failure/prerequisite behavior is undocumented, which is minor here.

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% and both schema and description state the same 'canonical autos.yahoo.com article URL' constraint. The description reinforces the domain restriction but adds no syntax or format detail beyond the schema, 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 ('Fetch a Yahoo Autos article's full content') and enumerates the returned fields (title, summary, author, dates, section, body paragraphs). It also distinguishes itself from siblings by naming yahoo_autos_home and yahoo_autos_category as discovery tools rather than article-fetch tools.

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?

Explicitly routes the agent: use yahoo_autos_home or yahoo_autos_category to discover story links, implying this tool is the second step once a URL is in hand. No explicit 'when-not-to-use' or exclusion, but the context is clear and complete.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?