Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmz_article

Fetch a TMZ article by its canonical URL to retrieve structured content such as title, authors, timestamps, image, paragraphs, and paywall status.

Instructions

Get TMZ article content. Returns one TMZ article by url, a canonical HTTPS tmz.com link of the form /<year>/<month>/<day>/<slug>/. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical TMZ article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 well by enumerating what the response contains (title, description, section, authors, publication/update times, image URL, paragraphs, paywalled flag). This gives solid behavioral context, though it omits error behavior for invalid/missing URLs and any auth or rate-limit notes.

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?

Three front-loaded sentences: purpose first, input format second, response shape third. No filler, no repetition of the name, and each sentence carries 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?

With no output schema, the description adequately covers the return shape while also stating the input format, so nothing essential is missing for correct invocation. The only gap is failure handling for invalid or non-canonical URLs.

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?

Schema coverage is 100% and the schema already labels the field 'Canonical TMZ article URL'. The description goes beyond that by spelling out the concrete URL pattern (`/<year>/<month>/<day>/<slug>/` on HTTPS tmz.com), which materially helps an agent construct a valid value.

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+resource ('Get TMZ article content. Returns one TMZ article by `url`') and clearly distinguishes itself from sibling tools like tmz_headlines, tmz_news, and tmz_sections, which return collections rather than a single article. An agent can select this without opening 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: the tool needs a canonical article URL, and the description specifies its shape. However, it never says when to use this vs. alternatives such as tmz_headlines or tmz_news, nor where to obtain a valid URL, which is the key prerequisite for a required-URL tool.

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