Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indiewire_author

Fetch an IndieWire author's public profile, including name, headshot, biography, social links, and recent articles, by providing their author page URL.

Instructions

Get an IndieWire author profile. Returns one IndieWire staff writer or contributor's public profile: name, headshot, biography, any listed social/contact links, and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical indiewire.com/author/<slug> URL
pageNo1-based page of recent articles to return; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 disclosure burden. It clearly signals a public read operation and specifies exactly what data will be returned, including the one-page limit on recent articles. It does not cover error or not-found behavior, but for a simple profile read this is reasonably transparent.

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 a single, well-structured sentence that front-loads the action and resource, then lists the return fields compactly. There is no redundant filler or unnecessary detail.

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 appropriately takes on the job of describing the return shape, listing concrete profile fields and the article page. It is nearly complete for a simple tool; minor omissions are exact article field details and behavior for invalid URLs.

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 parameters well. The description adds minor context by noting the articles are 'recent' and limited to 'one page,' but it does not substantially go beyond what the input schema already expresses.

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 ('IndieWire author profile') and enumerates the returned fields: name, headshot, biography, social/contact links, and recent articles. The IndieWire domain clearly distinguishes this from sibling author tools for other publications and from indiewire_article/headlines tools.

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 use case is implied by the name and description, but there is no explicit guidance about when to prefer this tool over alternatives such as indiewire_article or other author-profile tools. No exclusions or alternative conditions are stated, so an agent must infer the appropriate context.

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