Crawlora MCP

tmz_author

Read-only

Fetch a named person's TMZ profile hub and recent coverage by person slug or canonical /people/<slug> URL. Use tmz_article for a story or tmz_headlines, tmz_news, and tmz_sections to browse coverage.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tmz_author"
  }
}

Input Schema

Name	Required	Description
`url`	No	Canonical tmz.com/people/<slug> URL, optionally with a ?page= query parameter; alternative to slug
`page`	No	1-based page number; overrides any page number in url
`slug`	No	Person slug, e.g. dolly-parton

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / page / description

Added value: +"1-based page number; overrides any page number in url"

addedInput schema / properties / slug / description
```
Added value: +"Person slug, e.g. dolly-parton"
```

addedInput schema / properties / url / description

Added value: +"Canonical tmz.com/people/<slug> URL, optionally with a ?page= query parameter; alternative to slug"

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only profile is established. The description adds the shape of the result (profile hub plus recent coverage), but says nothing about pagination behavior despite a page parameter, auth, or rate limits. With annotations carrying the safety burden, this is an adequate-but-thin 3.

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?

Two tight sentences: the fetch semantics and identifier formats come first, the sibling routing second. Zero filler and nothing that needs to be read twice.

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?

Because an output schema exists, the description needn't explain return values, and it names both accepted identifier forms. It is complete enough to call correctly, with only pagination behavior left implicit between the page param and the description.

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%, so url, page, and slug are already fully documented, including the ?page= override and the dolly-parton style slug example. The description only echoes that slug or URL is accepted, adding no meaning beyond the schema. Baseline 3 applies.

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 (Fetch) plus the exact resource (a named person's TMZ profile hub and recent coverage), and pins the two accepted identifiers. An agent can distinguish it from tmz_article, tmz_headlines, tmz_news, and tmz_sections without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly routes the agent: use this for a person, use tmz_article for a story, and tmz_headlines/tmz_news/tmz_sections to browse coverage. The selecting conditions are named, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?