Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brisbanetimes_author

Fetch a Brisbane Times journalist profile from a canonical byline URL, returning name, bio, headshot, email, social links and recent stories.

Instructions

Get a Brisbane Times journalist profile. Returns a Brisbane Times journalist profile from url, a canonical https://www.brisbanetimes.com.au/by/<name>-<id> address: name, biography, headshot, email, social links and recent story cards with title, URL, summary and image. Fields appear only when the profile shows them; the sampled profile returned 10 stories.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Brisbane Times journalist URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/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 meaningful behavior: the exact fields returned (name, biography, headshot, email, social links, story cards), the fact that fields appear only when the profile shows them, and the observed story count. Missing auth or rate-limit notes, but strong on output behavior.

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?

Front-loaded with purpose then return shape in efficient sentences. The closing note about the sampled profile returning 10 stories is slightly incidental but still informative rather than wasteful.

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 single-parameter tool with no output schema, the description adequately documents both the input URL convention and the returned fields, leaving little an agent would need that 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 value by giving the canonical URL shape `https://www.brisbanetimes.com.au/by/<name>-<id>`, which the schema only labels as 'Canonical Brisbane Times journalist URL'.

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 (Get) and resource (Brisbane Times journalist profile) and pins it to the brisbanetimes.com.au domain, so it is distinguishable from the many other *_author siblings at a glance.

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

Usage Guidelines2/5

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

There is no explicit when/when-not guidance and no mention of alternatives such as brisbanetimes_article or brisbanetimes_headlines. Usage is only weakly implied by the required URL parameter.

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