Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mediaite_headlines

Fetch up to 20 recent Mediaite headlines for a required section slug (e.g., tv, politics), returning title, URL, and publication time.

Instructions

Get Mediaite section headlines. Returns up to 20 recent Mediaite stories for one category. section is required and takes a slug such as tv, politics, opinion or premium; any other value returns an invalid-parameter error. Each item has a title, URL and publication time, and may include author, summary and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesMediaite category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does reasonably well: it discloses the result cap (up to 20), the failure mode for bad section values, and the shape of returned items. It omits any auth, rate-limit, or caching behavior, but for a read-only headline feed this is solid disclosure.

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 compact sentences, front-loaded with the action and the required parameter, then the return shape. Nothing is padded, though the recitation of example slugs overlaps the enum and could be trimmed.

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?

There is no output schema or annotation coverage, so the description must explain returns, which it does (title, URL, publication time, optional author/summary/image) along with the count limit and error case. An agent has enough to invoke it correctly; only deep edge cases are unaddressed.

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 description coverage is 100% and the enum already enumerates all 15 valid slugs, so the schema does the heavy lifting. The description restates four example slugs (duplicating enum values) and adds only the invalid-value error behavior, which is marginal extra meaning over the schema.

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 Mediaite section headlines') and scopes it to one category, which separates it from the article/news siblings. It does not explicitly name how it differs from mediaite_sections or mediaite_news, so it stops short of a 5.

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 makes clear you must supply a section slug and that invalid values fail, which is useful usage context. However, it never says when to prefer this over mediaite_news, mediaite_article, or mediaite_sections, so the selection guidance 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