Skip to main content
Glama

Caelara Labs Social Analytics

creator_profile_composite

Creator profile audit: bio-link page audit + engagement benchmark

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

Input Schema

NameRequiredDescriptionDefault
urlYesLink-in-bio or profile page URL
avg_likesNoAverage likes per post
avg_viewsNoAverage views per post
followersNoFollower count
avg_commentsNoAverage comments per post

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and largely fails it. It does not disclose that the tool presumably fetches the external URL, whether the optional metrics are used as benchmark inputs versus measured values, or what the response looks like for a multi-part audit.

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 short line with the resource front-loaded and the two components enumerated after a colon, so there is no filler. It is efficient rather than padded, though the brevity borders on under-specification.

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

Completeness2/5

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

With five parameters, no annotations, and no output schema, the description should explain what the composite audit produces and how the optional engagement metrics are used. None of that is covered, so an agent cannot predict results or know when the composite is worthwhile.

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?

Schema description coverage is 100%, so all five parameters are already documented and the baseline is 3. The phrase 'engagement benchmark' mildly implies the avg_* and followers parameters feed a benchmark comparison rather than being measured, which adds a little meaning beyond the schema but is not made explicit.

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

Purpose3/5

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

The phrase 'Creator profile audit: bio-link page audit + engagement benchmark' names an action and two component analyses, which is more specific than the title alone. However, it never states in a sentence what the tool actually returns or does end-to-end, leaving an agent to infer that it fetches a profile page and scores engagement.

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 when-to-use guidance and no mention of when to prefer this composite over the sibling tools bio_link_auditor or engagement_rate_calc, which appear to cover the same sub-tasks individually. The only cue is the word 'composite' in the name, which the definition itself does not explain.

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