Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expresstribune_article

Fetch an Express Tribune story's full article data from its canonical tribune.com.pk URL, including title, authors, body paragraphs, images, timestamps, and paywall status.

Instructions

Get The Express Tribune article content. Returns one Express Tribune story by url, which must be a canonical tribune.com.pk/story/<id>/<slug> link. The response has the title, description, section, authors, publication and update times, lead image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Express Tribune story URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (title, description, section, authors, times, lead image, paragraphs) and flags a paywalled flag, warning the agent the body may be gated. It omits auth/rate-limit behavior, which keeps it short of a 5.

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 the input constraint, then the return shape. No filler and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter article fetcher with no output schema, the description covers both the input requirement and the response contents, including the paywall caveat. An agent has everything needed to call it correctly.

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?

Schema coverage is 100% with a single url parameter, so the baseline is 3. The description adds real meaning beyond the schema by specifying the exact canonical URL format (tribune.com.pk/story/<id>/<slug>), which the schema's terse label does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) plus resource (The Express Tribune article content) and clarifies it returns exactly one story keyed by URL. That effectively separates it from the expresstribune_headlines/news/sections siblings, though it never names them explicitly.

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?

Spells out the pre-condition for calling it: the url must be a canonical tribune.com.pk/story/<id>/<slug> link. It doesn't name alternatives or say when not to use this tool, so routing between it and the headline/list siblings is inferred rather than stated.

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

Deploy Server

Other Tools