Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mirror_author

Retrieve a Mirror author profile by slug or mirror.co.uk URL, returning name, job title, bio, contact details, and recent articles.

Instructions

Get a Mirror author profile. Returns a Mirror author profile by slug (for example neil-shaw) or by a mirror.co.uk author url; supply exactly one. The response has name, job_title, bio, email, twitter and one page of recent articles with title, URL and label. There is no paging, and unlisted contact details are omitted rather than raising an error.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical mirror.co.uk/authors/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. neil-shaw

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses returned fields, says there is no paging, and explains that unlisted contact details are omitted rather than causing an error. It does not explicitly describe invalid-author error behavior or auth/rate-limit constraints, so it is not fully comprehensive.

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 front-loaded, appropriately short, and every sentence contributes useful information: purpose, identifier rules, return shape, paging behavior, and omission behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool with no annotations and no output schema, the description provides enough return-value detail and behavioral caveats for an agent to invoke and interpret it correctly.

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 adds an important constraint beyond the schema: exactly one of url or slug must be supplied. It also reinforces the example slug format and the relationship between the two inputs.

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 begins with a specific verb and resource, "Get a Mirror author profile," and explains retrieval by slug or mirror.co.uk URL. This clearly separates it from sibling tools such as mirror_article, mirror_headlines, and mirror_sections.

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?

It gives clear context for use: retrieve a Mirror author profile and supply exactly one of slug or url. It lacks explicit when-not guidance or sibling alternatives, but the intended use case 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