Skip to main content
Glama

Caelara Labs Social Analytics

bio_link_auditor

Audit a link-in-bio page: link count, platforms, CTA and tracking

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": "bio_link_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesBio link page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It reveals what the audit inspects but says nothing about whether it fetches the page live, what happens with login-gated or unreachable URLs, whether it is rate-limited, or what the response contains — meaningful gaps for a fetch-and-inspect tool with no annotation safety profile.

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?

A single front-loaded sentence with zero filler; the scope is stated first and the enumerated checks follow. It is lean without being cryptic, though the fragment style gives no room for the operational caveats an agent would benefit from.

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

Completeness3/5

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

For a one-parameter tool this is close to adequate — the description plus schema tells an agent what to pass and roughly what will be reported. However, with no annotations and no output schema, the definition should still convey return-shape expectations and fetch/failure behavior, which it omits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter at 100% schema coverage, so the schema already defines `url` as "Bio link page URL". The description only reinforces that the target is a link-in-bio page rather than a profile or post URL; it adds no syntax, format, or validation nuance beyond the schema. Baseline 3 applies.

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?

Specific verb ("Audit") bound to a specific resource ("link-in-bio page"), plus an enumeration of what the audit covers: link count, platforms, CTA, tracking. An agent can tell exactly what this produces, though the description does not contrast it with any sibling.

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?

Usage is implied by the enumerated audit dimensions — you call it when you need link count, platform mix, CTA, or tracking presence on a bio page. There is no explicit when-not guidance, no prerequisite (e.g., page must be publicly reachable), and no named alternative, so an agent must infer the call conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources