Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stuff_author

Retrieve a Stuff (New Zealand) author profile by slug or canonical URL to get name, job title, location, bio, headshot, email, and recent stories.

Instructions

Get a Stuff author profile. Returns a Stuff (New Zealand) author's profile, looked up by slug (for example damien-venuto) or canonical url; exactly one is required. The response has the name, job_title, location, biography, headshot, email and recent stories. Fields show only what the profile has; shared team bylines usually carry just a job title. An unknown author returns not found.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical stuff.co.nz/authors/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. damien-venuto

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?

With no annotations, the description carries the full burden and does well: it discloses the return fields, warns that fields are sparse ('shared team bylines usually carry just a job title'), and specifies the not-found behavior. It omits only auth/rate-limit context, which is minor for a read.

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?

Front-loads the purpose, then the lookup keys, then the response shape, then edge cases. Three tight sentences with no filler; each sentence adds information an agent needs.

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 read-only profile tool with no output schema and no annotations, the description covers the return fields and edge cases well enough to call it correctly. It is nearly complete, missing only tangential operational details.

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 already 100%, so the baseline is 3, but the description adds real meaning: it clarifies that exactly one of slug/url is required (the schema marks neither as required) and gives a concrete slug example. This resolves ambiguity the schema leaves open.

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 Stuff author profile') and immediately scopes it to Stuff (New Zealand), distinguishing it from the many other *_author siblings tied to different outlets. An agent knows exactly 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 description supplies the lookup conditions ('by slug ... or canonical url; exactly one is required') which imply when the tool applies, but it names no alternative sibling and gives no explicit when-to-use/when-not guidance. Usage is inferable rather than stated.

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