Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deadline_news

Retrieve Deadline Hollywood top stories from its main feed, with title, URL, summary, publication time, author, and image for each item. Use deadline-headlines for a single section or vertical.

Instructions

Get Deadline top stories. Returns the current Deadline Hollywood top stories from its main feed. Each item has its title, URL, summary, publication time, author and image. Takes no parameters; use deadline-headlines for a single section or vertical.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 disclosure burden. It helpfully states 'Takes no parameters' and enumerates the returned fields, but says nothing about freshness, caching, rate limits, or that this is a read-only feed retrieval.

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 tight sentences, front-loaded with purpose and ending with the sibling routing. 'Returns the current Deadline Hollywood top stories from its main feed' mildly restates the opening clause, a small 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 param-free feed reader with no output schema and no annotations, the description covers purpose, return contents (title, URL, summary, time, author, image), param-free invocation, and the sibling alternative. Freshness expectations are the only notable omission.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly confirms this ('Takes no parameters'), leaving no ambiguity about invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 top stories') and scopes it to the main feed rather than a section. It explicitly names the sibling `deadline-headlines` and the distinction (single section/vertical), so an agent can separate it from the other Deadline tools without opening a schema.

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

Usage Guidelines4/5

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

Names the alternative tool and the condition that selects it ('use deadline-headlines for a single section or vertical'), which gives clear routing guidance. It does not spell out an explicit when-not case beyond that, so it falls just short of the top mark.

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