Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nypost_author

Fetch a New York Post author profile from a canonical author URL, returning name, biography, image, social links, and recent articles.

Instructions

Get a New York Post author profile. Returns a New York Post author profile from a required url in the form https://nypost.com/author/<slug>/. The response has name, biography, image_url, social_links and recent articles. Staff and wire bylines often have no headshot or bio, and each article's published_at is the page's date text such as September 20, 2026 | 10:06pm.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical New York Post 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?

With no annotations, the description carries the full burden and does well: it names the response fields, discloses the real edge case that staff/wire bylines often lack headshot or bio, and documents the quirky `published_at` date format. It omits only operational concerns like auth or rate limits, which is minor for a read-only profile fetch.

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 front-loaded sentences that each add distinct value: purpose, input form, and output/edge-case detail. No padding, though the output enumeration and the date-format remark are somewhat dense.

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?

No output schema exists, so the description must describe returns, and it does (name, biography, image_url, social_links, recent articles) plus edge cases. Complete enough to call correctly; only the absence of any mention of limits/pagination keeps it from 5.

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%, so the baseline is 3, but the description goes beyond the schema's terse 'Canonical New York Post author URL' by giving the concrete `https://nypost.com/author/<slug>/` form, which materially helps correct invocation.

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 New York Post author profile') and immediately scopes it as an author-profile fetch, distinguishing it from the article/headline/section siblings. An agent can tell what it retrieves 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 required URL form is given, which implies when the tool applies, but there is no explicit when-to-use or when-not guidance and no reference to alternative tools (e.g., the many other *_author siblings or nypost_article). Usage is only implied.

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