Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmz_headlines

Access real-time TMZ headlines for news or sports. Pull clean, structured data including titles, summaries, and URLs from the popular gossip site.

Instructions

Get TMZ section headlines. Returns the current headlines for one TMZ section. section is required and must be news or sports. Each item has its title, URL and, where available, a summary, author, publication time, image and type, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesTMZ section 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, the description carries the burden and does useful work: it discloses the returned shape per item (title, URL, and optional summary, author, publication time, image, type) and that the response echoes the section. It does not explicitly state the operation is a plain read, but 'Get' makes that clear and no contradictory behavior is implied.

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?

Front-loaded with the purpose, then the required parameter, then the return shape. Efficient overall; the return-fields sentence is slightly dense but each clause conveys distinct information.

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, so the description appropriately covers return values and the required parameter. For a single-parameter headline reader this is nearly complete, with only the sibling/alternative routing left implicit.

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 coverage is 100% and the enum (news/sports) is already defined in the schema. The description restates that valid values are news or sports but adds no syntax or format meaning beyond the structured field, so the baseline 3 applies.

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+resource: 'Get TMZ section headlines' and clarifies it returns 'the current headlines for one TMZ section.' Clear and specific, but does not explicitly differentiate from siblings like tmz_sections or tmz_news.

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?

Usage is implied: call this to fetch headlines for a TMZ section. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as tmz_sections (to discover sections) or tmz_article (to fetch a full story).

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