Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

france24_headlines

Retrieve France 24 English-edition headlines by section, including Africa, Europe, or Business-Tech. Returns title, URL, summary, publication time, and author for each item.

Instructions

Get France 24 section headlines. Returns the latest France 24 English-edition headlines for one section. section is required and must be one of africa, americas, asia-pacific, europe, france, middle-east, business-tech, culture, environment, sport, live-news or tv-shows. Each item has its title, URL, summary, publication time and author.

Input Schema

NameRequiredDescriptionDefault
sectionYesFrance 24 section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the output fields (title, URL, summary, publication time, author) and implies a read-only operation, but does not mention rate limits, pagination, authentication, or the number of items returned, leaving gaps in behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and is reasonably concise. However, listing all 12 enum values is redundant given the schema already defines them, adding unnecessary length.

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 one-parameter headline tool with no output schema, the description covers the essential information: what it returns, the required parameter, and the allowed values. It lacks details on the number of headlines or pagination, but these are minor for a basic retrieval tool.

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 has 100% description coverage with the enum defined. The description repeats the enum values and required status, adding no new semantic meaning beyond what the schema already provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb 'Get' and resource 'France 24 section headlines', and specifies it returns latest headlines for one section. However, it does not distinguish itself from sibling tools like france24_news or france24_sections, so sibling differentiation is missing.

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?

No explicit when-to-use or when-not-to-use guidance is provided. It does not mention any alternatives or conditions for selecting this tool over other France 24 headline/news tools. Usage is implied only by the required section parameter.

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