Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indiewire_sections

Lists IndieWire's 32 editorial categories with slugs, display names, feed URLs, and nested roots for querying headline feeds.

Instructions

Get IndieWire sections. Lists IndieWire's 32 editorial categories accepted by indiewire-headlines, such as analysis, box-office, festivals, interviews, obituary and trailers. Each entry has a slug, display name and the category feed url. Categories nest under the roots news, features, awards and criticism.

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 full burden, and it does disclose the return shape ('slug', display 'name', category feed 'url') and the catalog size (32 categories) plus the nesting roots. It omits any statement about safety/auth/rate limits, but for a zero-parameter read-only listing the disclosed structure is the behavior an agent actually needs.

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?

Four tightly packed sentences, zero filler: purpose first, then catalog scope, then the record fields, then the taxonomy roots. Every sentence adds distinct information an agent can act on.

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?

With no output schema and no annotations, the description compensates by describing the returned fields and the category hierarchy, and it links the tool to its consumer (indiewire-headlines). Nothing an agent needs in order to call this correctly is missing.

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, which is the baseline-4 case; there are no arguments whose semantics could be under-documented. The description's mention of accepted category slugs is about outputs, not inputs, which is consistent with the empty schema.

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 IndieWire sections') and immediately scopes the content: 32 editorial categories accepted by `indiewire-headlines`. It names concrete example slugs and the four root categories, so an agent distinguishes it from indiewire_headlines, indiewire_article and indiewire_news without opening any 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?

The phrase 'categories accepted by `indiewire-headlines`' implicitly tells the agent when to reach for this tool: to resolve a category slug before calling the headlines tool. That is clear routing context, but there is no explicit when-not guidance and no enumeration of alternative discovery paths.

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