Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metro_article

Retrieves Metro article metadata and body paragraphs from a canonical URL, including live-blog entries. Provides structured JSON for headlines, authors, and content.

Instructions

Get Metro article content. Returns public Metro article metadata (headline, description, section, authors, publish/update times, lead image) and body paragraphs from a canonical article URL. Metro articles are free to read; live-blog entries are included in the body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Metro article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds value by stating that content is public and free to read, and that live-blog entries are included in the body. However, it does not mention whether the operation is read-only (though implied by 'Get'), any error conditions, or whether pagination exists for long bodies. This is adequate but not comprehensive.

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 core function, followed by concise detail. No fluff, no redundancy. Every clause earns its place.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description explains the return content in useful detail (metadata fields, body paragraphs, live-blog inclusion). It does not describe output format or potential pagination, but for an article fetch it is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides a complete description of the only parameter ('Canonical Metro article URL'), achieving 100% coverage. The description adds minimal extra meaning—only echoing 'canonical article URL'. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description states a specific verb ('Get'), resource ('Metro article content'), and enumerates exactly what is returned (metadata fields and body paragraphs). It clearly identifies the scope (public Metro articles) and differentiates from siblings by naming 'Metro' and '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.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for Metro specifically or suggest other tools for headlines, authors, or sections. The context of siblings like nzherald_article and apnews_article implies differentiation, but this is not made explicit.

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