Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cna_author

Retrieve a CNA author's profile by slug or URL to access name, job title, bio, email, image, and recent articles.

Instructions

Get a CNA author profile. Returns a CNA correspondent's or contributor's profile, identified by slug (such as aqil-haziq-mahmud) or a channelnewsasia.com/author/<slug> url; exactly one is required. The response has name, job title, bio, email, image and the latest page of bylined articles, each with title, URL and label. External Commentary contributors usually have only a name and articles.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical channelnewsasia.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. aqil-haziq-mahmud

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 disclose the response shape (name, job title, bio, email, image, latest bylined articles) plus an edge-case caveat that External Commentary contributors usually have only name and articles. It omits auth/permission requirements and error behavior for bad slugs, keeping it short of a 5.

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 with no filler; the identification rule and return contents come first, the contributor caveat last. Dense but every sentence earns its place and there is no redundancy.

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 lookup with no output schema and no annotations, the description adequately covers inputs, the exactly-one constraint, the return payload, and one known edge case. Minor gaps remain around invalid-slug behavior, but nothing an agent needs to call it is missing.

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 real meaning beyond the schema: it gives a concrete slug example, specifies the full URL form, and states the mutual-exclusivity rule ("exactly one is required") that the schema's empty `required` list does not convey.

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 CNA author profile") and immediately narrows the scope to correspondents/contributors, which distinguishes it from sibling article/news/headline tools. An agent can tell what it returns 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 explains the identification mechanism but never states when to reach for this tool versus siblings such as cna_article or cna_headlines, or versus other outlets' author tools. Usage is implied by the tool's name rather than spelled out.

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