Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

phillyinquirer_article

Retrieve structured Philadelphia Inquirer article content from a canonical inquirer.com story URL, including title, authors, timestamps, section, lead image, and body paragraphs in reading order.

Instructions

Get Philadelphia Inquirer article content. Returns a Philadelphia Inquirer story by canonical inquirer.com url ending in -<yyyymmdd>.html: title, description, publication and update times, section, authors, lead image and body paragraphs in reading order. Captions, teasers and comments are excluded. Associated Press /wires/ pages, section pages and author pages return 400.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Philadelphia Inquirer story URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does most of the work: it discloses the returned field set, states that captions, teasers and comments are excluded, and documents the failure mode (400) for out-of-scope URL types. It does not mention paywall/login behavior, rate limits, or what happens with malformed-but-story-shaped URLs, which for a news article fetcher would be valuable.

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?

Three sentences, each load-bearing: what it gets, what comes back, what is excluded and what fails. The return-content sentence is front-loaded right after the purpose statement, and no sentence is filler.

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 tool with no annotations and no output schema, the description compensates by describing the payload structure inline and flagging error conditions. Nothing an agent needs to call it correctly — or to know whether a given URL is eligible — is missing.

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% and there is only one parameter, so baseline is 3; the description earns a step above by specifying the exact URL shape required (`-<yyyymmdd>.html` suffix) and naming URL classes that are rejected. That is real semantic guidance an agent cannot derive from the schema field text alone.

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 ("Get Philadelphia Inquirer article content") and immediately enumerates what a returned story contains: title, description, timestamps, section, authors, lead image, and body paragraphs in reading order. An agent can distinguish this from phillyinquirer_headlines / _news / _sections / _author without opening any schema.

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?

Gives a precise precondition for use: the url must be a canonical inquirer.com story URL ending in `-<yyyymmdd>.html`. It also explicitly excludes three URL classes (AP `/wires/`, section pages, author pages) that return 400. What it lacks is explicit routing to siblings — e.g. telling the agent to use phillyinquirer_headlines or _news to discover URLs before calling this.

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