Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ft_headlines

Fetch stories from a Financial Times section using a section slug, returning titles, URLs, summaries, tags, publication times, and lead images.

Instructions

Get the latest stories in a Financial Times section. Returns one page of a Financial Times section front: each story's title, canonical URL, summary, section tag, publication time, and lead image. Section must be a slug returned by /ft/categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResults page
sectionYesSection slug from /ft/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool returns one page of a section front, names each story field, and constrains the section input to known slugs. It does not cover error behavior or rate limits, but the read-only nature and page behavior are sufficiently clear.

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, each earning its place: the first states the action and resource, the second details the return shape and prerequisite. No filler or redundancy.

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 two-parameter list endpoint with no output schema, the description adequately explains the return payload, pagination, and the required slug source. It omits page-size or error details, but an agent can invoke it correctly after calling /ft/categories.

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 baseline is 3. The description reinforces that section must come from /ft/categories, matching the schema, and adds no substantial new meaning for the page parameter beyond the schema's 'Results page'.

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?

The description states a specific verb and resource: 'Get the latest stories in a Financial Times section' and enumerates the returned fields. It is clear and distinguishes itself from non-FT sibling tools by naming Financial Times and /ft/categories, but it does not explicitly contrast with close siblings like ft_news.

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

Usage Guidelines3/5

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

The description gives an explicit prerequisite for the primary parameter: 'Section must be a slug returned by /ft/categories.' However, it does not explain when to prefer this tool over alternatives such as ft_news or ft_search, leaving the 'when-to-use' guidance largely implied.

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