Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mediaite_sections

Lists Mediaite section slugs to use as the section parameter for mediaite-headlines, including tv, politics, opinion, crime, premium, and election-2020.

Instructions

Get Mediaite sections. Lists the 15 Mediaite category slugs accepted as section by mediaite-headlines, such as tv, politics, opinion and crime. Each entry has its slug, display name and url. premium is the Mediaite One Sheet newsletter category, and election-2020 is a legacy category that still publishes occasionally.

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?

With no annotations, the description carries the full burden and does reasonably well: it discloses the return shape (slug, name, url), explains what the `premium` category represents, and flags `election-2020` as a legacy category that still publishes occasionally. It omits nothing critical for a read-only listing, though it says nothing about caching or freshness.

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 tight sentences, front-loaded with what the tool is, then the relationship to mediaite-headlines, then the output fields, then the two edge-case categories. No filler or redundancy.

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?

For a zero-parameter listing tool with no output schema, the description covers purpose, output fields, and edge-case categories, which is everything an agent needs to select and use it 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 usefully enumerates sample slug values and clarifies the semantics of two non-obvious entries, which is value beyond 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 Mediaite sections') and immediately scopes it: 'Lists the 15 Mediaite category slugs accepted as `section` by `mediaite-headlines`.' This distinguishes it from sibling tools like mediaite_article and mediaite_headlines without requiring the 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?

It clearly connects the output to its consumer by naming `mediaite-headlines` and its `section` parameter, implying this is the discovery step before fetching headlines. It stops short of an explicit 'call this before X' instruction or any when-not-to-use guidance, so it is clear context rather than full routing.

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