Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deadline_headlines

Fetch current Deadline section news by slug, returning title, URL, summary, author, image, and publication time for film, TV, awards, box office, and more.

Instructions

Get Deadline section headlines. Returns the latest Deadline headlines for one section or vertical. section is required and takes one of 48 slugs, for example film, tv, box-office, awards, casting, reviews or obituaries. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesDeadline 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 full behavioral burden. It helpfully enumerates the returned fields (title, URL, summary, publication time, author, image), but says nothing about ordering, pagination, result counts, or auth requirements for a headlines feed.

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 that are front-loaded with the core action, then the required parameter, then the return shape. Efficient, though the enumeration of example slugs is slightly redundant with the schema enum.

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?

With no output schema, the description compensates by listing the item fields, and the single required param is fully covered by the schema. For a simple read-only headlines tool this is nearly complete, lacking only feed-level details like count or ordering.

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 already lists all 48 slugs plus the required flag, so the schema does the heavy lifting. The description restates that section is required and gives example slugs, adding marginal value over the structured data.

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 and resource ('Get Deadline section headlines') and clarifies the scope is one section or vertical. It does not, however, distinguish itself from close siblings like deadline_news or deadline_sections, so an agent still has to infer the boundary.

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 notes that section is required and takes one of 48 slugs, which implies the use case is per-section headline retrieval. It never states when to prefer this over deadline_news or deadline_sections, so usage is only 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