Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

pagesix_author

Retrieve a Page Six author profile from a canonical URL, returning name, biography, image URL, social links, and recent articles in clean JSON.

Instructions

Get a Page Six author profile. Returns a Page Six author profile from a required url in the form https://pagesix.com/author/<slug>/. The response has name, biography, image_url, social_links and recent articles. An RSS feed link is the only social link always present, and each article's published_at is the page's date text such as September 23, 2026 | 8:16pm.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Page Six author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it delivers useful behavioral detail: the exact return fields, the caveat that only an RSS link is always present in social_links, and the fact that published_at is raw page date text ('September 23, 2026 | 8:16pm') rather than a normalized timestamp. It does not mention permissions or rate limits, but for a public profile fetch that is minor.

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 sentences, front-loaded with the purpose, then input format, then response shape. The published_at format detail is narrow but genuinely useful for downstream parsing; no filler sentences.

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 must convey the return shape, and it enumerates name, biography, image_url, social_links and recent articles. That is close to complete for calling and consuming the tool, though it does not state pagination/limits on the 'recent articles' list.

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 single parameter is documented as 'Canonical Page Six author URL'. The description adds value beyond that by giving the concrete URL shape with the `<slug>` placeholder, which tells the agent what a valid value looks like.

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 and resource ('Get a Page Six author profile') and immediately names the exact artifact it returns. Within the pagesix_* family it is clearly distinct from pagesix_article, pagesix_news and pagesix_sections, so an agent can route 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?

The URL template 'https://pagesix.com/author/<slug>/' implies the required input, but there is no explicit when-to-use guidance or mention of alternatives (e.g., use pagesix_article for individual stories). Usage is only implied by the resource being fetched.

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