Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

politico_author

Fetch a Politico staff author's public profile—name, job title, bio, headshot, and recent bylined articles—using their slug or URL.

Instructions

Get a Politico staff author profile. Returns one Politico staff author's public profile: name, job title, bio, headshot, and their most recent bylined articles. Politico staff pages expose a fixed-size recent-articles list with no pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical www.politico.com/staff/<slug> URL, as an alternative to slug
slugNoPolitico staff slug, e.g. mark-satter

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?

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds meaningful context by noting the profile is public, listing the returned fields, and explicitly warning that the recent-articles list is fixed-size with no pagination. It does not cover error or rate-limit behavior, but that is a minor gap for a simple read tool.

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?

The description is three sentences with no filler. The first sentence front-loads the action and resource, the second lists return fields, and the third provides a useful pagination constraint.

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?

For a two-parameter read-only tool with no output schema, the description covers purpose, return fields, and the pagination limitation. A minor gap is that it does not explicitly state that exactly one of `slug` or `url` must be provided, though the schema hints at this.

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 the schema already documents both `slug` and `url`. The description adds no additional parameter-level meaning, though it does imply the tool identifies a single author. The one-of requirement is not explicitly stated, but the schema's 'alternative to slug' wording provides a baseline.

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?

The description states a specific verb ('Get') and resource ('Politico staff author profile'), then enumerates the exact returned fields: name, job title, bio, headshot, and recent bylined articles. This clearly distinguishes it from article, headline, topic, and category siblings.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: when you need a Politico staff author's public profile and recent bylines. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous.

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