Retrieve a Global News author's biography, byline metadata, and recent articles from a canonical author URL for structured JSON output.
Get a Global News author profile. Returns a Global News author's byline metadata, biography, and recent articles from a canonical author URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Global News author 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 full burden. It does not disclose any behavioral traits such as permission requirements, rate limits, or handling of invalid URLs. It only states what the tool does without additional context on side effects or edge cases.
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?
The description is two sentences, front-loaded with the action and resource, and lists the return types without any fluff. Every sentence contributes to understanding the tool.
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 single-parameter tool with no output schema, the description provides a reasonable summary of what is returned (byline metadata, biography, recent articles). While it could be more specific about the response structure, it is sufficient for an agent to understand the tool's function.
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?
The schema already fully documents the 'url' parameter (100% coverage), and the description merely echoes 'from a canonical author URL' without adding meaningful new semantics. The description adds little beyond the schema definition.
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?
The description states a specific verb ('Get'), a specific resource ('Global News author profile'), and explicitly lists the returned content (byline metadata, biography, recent articles). This clearly distinguishes it from sibling tools like globalnews_article or globalnews_headlines.
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?
The usage is implied: you use this when you want author profile information for Global News. However, there is no explicit mention of when not to use it or alternatives (e.g., when to choose globalnews_article instead). The guidance is adequate but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.