Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sun_headlines

Retrieve current headlines for a selected The Sun section, returning each item's title and URL. For news, include summary, author, publication time, and image when available.

Instructions

Get The Sun section headlines. Returns the current headlines for one The Sun section. section is required and takes one of news, politics, royal-family, sport, showbiz, money, tech, fabulous, travel or health. Every item has its title and URL. The news section also carries summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Sun section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/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, and it does disclose the return shape: every item has title and URL, with summary/author/publication time/image only in the news section. It omits freshness, rate limits, and any auth considerations, so it is adequate but incomplete.

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?

Three sentences, front-loaded with the resource and scope, and the parameter detail follows logically. The opening two sentences overlap ('Get The Sun section headlines' / 'Returns the current headlines for one The Sun section'), a minor 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?

There is no output schema and no annotations, so the description must cover returns, which it does concisely (title/URL always; extra fields in news). For a single-parameter read tool this is nearly complete, missing only pagination/volume expectations.

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 the enum is already documented, so baseline is 3. The description goes slightly further by spelling out the accepted slugs and, more usefully, flagging that choosing 'news' yields extra fields (summary, author, time, image), which informs parameter selection.

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 Sun section headlines', 'Returns the current headlines for one The Sun section') and scopes it to a single section. The scope is precise enough to separate it from article-level siblings, though no sibling (e.g. sun_news, sun_article) is named explicitly.

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?

It says what the tool does but never states when to choose it over sun_news, sun_sections, or sun_article. No when-to-use, when-not-to-use, or alternative routing is provided; usage is only implied by the tool's nature.

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