Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deadline_sections

List all 48 Deadline sections accepted by headline feeds, including 28 editorial categories and 20 verticals with slugs, names, and feed URLs.

Instructions

Get Deadline sections. Lists the 48 Deadline sections accepted by deadline-headlines: 28 editorial categories such as news, reviews and festivals, and 20 verticals such as film, tv, business and awards. Each entry has the slug, name and feed url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/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 entry has slug, name, feed url) and the total count (48) split into editorial categories and verticals, which is useful given there is no output schema. It does not mention read-only nature explicitly, but 'Get' implies it and no mutation is suggested.

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

Conciseness5/5

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

Three tightly written sentences that front-load the purpose, then add a useful breakdown of the 48 sections, and finish with the return fields. No redundancy or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (no parameters, no output schema, no annotations), the description provides enough detail for an agent to understand what the tool returns and why it exists. The only minor omission is whether these sections apply to other Deadline endpoints, but that is not critical to using this tool correctly.

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 avoids discussing parameters and instead focuses on return values, which is appropriate for a parameterless lookup.

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 (Get) and resource (Deadline sections), and immediately ties it to the sibling tool `deadline-headlines` by saying these are the sections it accepts. An agent can distinguish this from other Deadline tools like `deadline_news` or `deadline_article`.

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?

Explicitly says the list is accepted by `deadline-headlines`, which gives clear context for when to use it (to discover valid section identifiers). It does not mention whether other Deadline tools also accept these sections or provide any when-not-to-use guidance, so it falls short of a 5.

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