Fetch Android Authority article metadata and body paragraphs from a canonical URL to read, parse, or analyze public article content as clean JSON.
Get Android Authority article content. Returns public Android Authority article metadata and body paragraphs from a canonical article URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Android Authority article URL |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It discloses that the tool returns 'public' metadata and body paragraphs, implying read-only, no-auth access. It stops short of stating idempotence, error behavior, or payload specifics beyond the two components.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action, no filler. Every clause adds information about input or output.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with no output schema, the description explains the essential return shape (metadata + body paragraphs) and input constraint. It leaves minor gaps – exact metadata fields and failure behavior – but the definition is functionally complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single 'url' parameter, so the baseline is 3. The description's 'canonical article URL' phrase matches the schema and adds no new format or semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Get Android Authority article content' and clarifies 'Returns public Android Authority article metadata and body paragraphs'. This clearly distinguishes it from sibling list tools like androidauthority_headlines and androidauthority_sections by focusing on a single canonical article URL.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage: the description says the input is a 'canonical article URL', indicating the tool should be used only when a specific article URL is in hand. However, it does not explicitly mention when to use it versus sibling article tools (e.g., androidauthority_headlines) or state exclusions, leaving the agent to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.