Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reuters_section

Retrieve recent articles from a selected Reuters section, returning canonical URLs, update times, and image details. Use for structured data feeds without titles.

Instructions

Get recent articles in a Reuters section. Returns a page of one top-level Reuters section's recent articles: canonical URL, update time, lead image URL, and image caption. This feed does not publish titles; use /reuters/articles for a title-bearing index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResults page, 100 items per page
sectionYesTop-level Reuters section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses a key limitation—this feed does not publish titles—and specifies the fields returned. It could go further on pagination or error behavior, but the core behavioral traits are clearly communicated.

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, no filler. The main action is front-loaded, return fields are listed compactly, and the important limitation plus alternative is placed at the end. Every sentence 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?

The tool has only two parameters, one of which is an enum, and no output schema, so the description must explain return values—it does, listing the four returned fields. It also covers the title limitation and points to the sibling tool. It is nearly complete, though it does not describe pagination behavior beyond what the schema already states.

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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds context by clarifying that the tool returns a page of one top-level section's articles, but it does not add meaningful parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Get recent articles in a Reuters section.' It clearly states the tool returns a page of one top-level Reuters section's recent articles and lists the exact fields returned, distinguishing it from the sibling reuters_articles tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly names the alternative tool for title-bearing indexes: 'use /reuters/articles for a title-bearing index.' This gives the agent a clear condition for choosing between this tool and a sibling, which is exactly the kind of when-to-use guidance needed.

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