Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmz_news

Fetch current TMZ celebrity news top stories with titles, URLs, authors, summaries, publication times, and image URLs for quick headline tracking.

Instructions

Get TMZ top stories. Returns the current TMZ celebrity news top stories. It takes no parameters. Each item has its title, URL and, where available, an author such as TMZ Staff, a summary, publication time and image URL. Use the headlines endpoint with sports for sports stories.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the item shape (title, URL, optional author like 'TMZ Staff', summary, publication time, image URL) and that no parameters are taken, but says nothing about freshness/latency, rate limits, item count, or pagination.

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?

Four short sentences, front-loaded with the purpose before the return detail and the sibling hint. There is mild redundancy between 'Get TMZ top stories' and 'Returns the current TMZ celebrity news top stories,' but nothing wasteful enough to hurt scanning.

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?

With no output schema, the description properly documents the returned fields, and with zero parameters there is no input contract to explain. It is essentially complete for a simple no-arg feed, missing only volume/freshness expectations.

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 has zero parameters, so per the baseline a 4 is appropriate. The description explicitly confirms 'It takes no parameters,' which removes any doubt about how to invoke it.

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 TMZ top stories') and names the sibling source it is distinct from (the headlines endpoint for sports). An agent can tell it is a top-stories feed rather than a section or article lookup, though it doesn't explicitly contrast with tmz_headlines/tmz_sections/tmz_article.

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?

It gives one routing hint ('Use the headlines endpoint with `sports` for sports stories'), which implies this tool is for general entertainment/celebrity coverage. But there is no explicit when-to-use/when-not guidance for the other close siblings (tmz_article, tmz_sections, tmz_author), so selection still requires inference.

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