Extract public Express Tribune story metadata and article body paragraphs from a canonical tribune.com.pk/story URL for research, summarization, or monitoring.
Get The Express Tribune article content. Returns public story metadata and body paragraphs from a canonical tribune.com.pk/story// URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Express Tribune story URL |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses the return shape (public story metadata and body paragraphs), but says nothing about permissions, rate limits, paywall handling, or failure modes for malformed URLs.
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 purpose and followed by the return contract, with zero filler or repetition.
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 fetch tool with no output schema, the description covers both what it takes (canonical URL form) and what it gives back (metadata plus body). Only the absence of any usage/alternative guidance keeps it from being fully complete.
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% and the single param is already documented, so baseline is 3. The description goes beyond it by specifying the canonical URL pattern tribune.com.pk/story/<id>/<slug>, which tells the agent the expected form of the required input.
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 (Get) and resource (Express Tribune article content), and the name/description distinguish it cleanly from siblings like expresstribune_headlines, expresstribune_news, and expresstribune_author. It does not explicitly name or route against those siblings, so it stops short of a 5.
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?
There is no explicit when-to-use guidance, no mention of alternatives (e.g., headlines for listing, author for bylines), and no stated prerequisites. The URL-format hint implies input shape but not selection context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.