Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

time_headlines

Fetch current TIME section headlines by section slug; returns titles and URLs for news, politics, world, business, technology, health, entertainment, sports, ideas, or climate.

Instructions

Get TIME section headlines. Returns the current headlines for one TIME section. section is required and takes one of news, politics, world, business, technology, health, entertainment, sports, ideas or climate. Each item has its title and URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesTIME RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return shape ('Each item has its title and URL') and that results are 'current', which is useful. It says nothing about authentication, rate limits, or ordering, so it remains a minimum-viable disclosure for a read operation.

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 short sentences, front-loaded with the core action; the return-shape note is a useful addition. There is mild redundancy between 'Get TIME section headlines' and 'Returns the current headlines for one TIME section'.

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 single-parameter, no-output-schema tool, the description covers the input constraint and the return fields (title and URL), which is what an agent needs to call and interpret it. Only the sibling differentiation and operational details are absent.

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 coverage is 100% and the enum is fully documented in the schema; the description merely restates the same enum values. It adds no syntax or format meaning beyond the structured data, so baseline 3 applies.

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?

States a specific verb+resource ('Get TIME section headlines') and scopes it to 'one TIME section', so an agent knows exactly what it fetches. It doesn't explicitly distinguish itself from siblings like time_news or time_sections, hence not a 5.

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?

Usage is implied by the section-scoping and the enumerated slugs, indicating a per-section headline lookup. However there is no explicit when-to-use guidance and no mention of how it differs from time_news, time_sections, or time_article, which are the obvious alternatives.

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