Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_bio_link_auditor

Audit a link-in-bio page to count links, identify platforms, and check CTA and tracking setup.

Instructions

[Social Analytics] Audit a link-in-bio page: link count, platforms, CTA and tracking Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://social.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesBio link page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it discloses measured latency (p50 12 ms, p95 14 ms) and the upstream endpoint, which is useful operational context. It does not state read-only nature, rate limits, auth requirements, or failure modes, leaving meaningful behavioral gaps for a no-annotation tool.

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?

Two compact sentences front-load the purpose before the benchmark and endpoint metadata. The benchmark citation and endpoint are secondary but short enough not to obscure the core statement.

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?

The tool is simple (one URL parameter, no output schema), and the enumeration of audited aspects gestures at what comes back, but the actual return structure, error behavior, and any constraints are unaddressed. Adequate for invocation, thin for interpreting results.

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?

With a single required parameter at 100% schema description coverage ('Bio link page URL'), the schema already fully documents the input and the description correctly adds nothing redundant. The only shortfall is that it doesn't clarify URL format expectations (e.g., scheme, trailing path).

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?

States a specific verb and resource ('Audit a link-in-bio page') and enumerates the audited dimensions (link count, platforms, CTA, tracking), which lets an agent distinguish it from the social profiling and card-extraction siblings. It stops short of explicitly contrasting with a similarly named sibling like the broken-link scanner.

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 guidance on when to choose this over alternatives such as caelara_seo_broken_link_scanner, nor any stated prerequisites or exclusions. Usage is only implied by the name and the phrase 'link-in-bio page'.

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