Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sbsnews_author

Fetch an SBS News author profile by canonical collection URL, including bio, headshot, and paginated article links.

Instructions

Get an SBS News author profile. Returns an SBS News byline collection by canonical url, for example https://www.sbs.com.au/news/collection/jennifer-scherer: name, headshot, biography and the articles on the requested archive page (1-based, default 1), with has_next_page for paging. Articles are limited to SBS News article, Insight and Dateline links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "sbsnews_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical SBS News author collection URL
pageNo1-based author archive page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.8/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 shape (name, headshot, biography, articles), the paging behavior (1-based page, default 1, has_next_page), and a real scope constraint (articles limited to SBS News article, Insight and Dateline links). It omits auth/rate-limit or error behavior, so not 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?

One front-loaded paragraph that leads with the purpose and then layers in return fields, paging, and content limits. Dense but every clause carries information; the long trailing sentence is the only mild structural weakness.

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 and no annotations, the description must define returns, and it does (fields plus has_next_page). Two parameters, both explained, and content scope stated. Only the absence of permission/error context keeps it from a 5.

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 a 3 is the baseline, but the description adds value: it supplies a concrete canonical URL example for `url` and clarifies that `page` is 1-based with a default of 1 and drives has_next_page. That goes beyond the schema's short parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Get an SBS News author profile") and then specifies exactly what is returned (byline collection keyed by canonical URL). It is clearly distinct from siblings like sbsnews_news or sbsnews_headlines, though it never names an alternative explicitly.

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?

It implies when to use it — fetching a byline/author archive keyed by a canonical collection URL — and gives a concrete example URL, but there are no explicit when-not-to-use rules or routing to sibling tools such as sbsnews_article or sbsnews_headlines. Adequate but inferential.

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