Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_creator_profile_composite

Audit a creator's bio-link profile and benchmark engagement using provided follower, like, view, and comment metrics.

Instructions

[Social Analytics] Creator profile audit: bio-link page audit + engagement benchmark 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_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 observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses that the tool makes a call to https://social.caelaralabs.com, which is genuinely useful context, but it says nothing about auth requirements, whether the operation is read-only, cost, or what happens to supplied metrics versus fetched ones. The latency figures read as marketing rather than operational guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in a single compact clause, but the trailing benchmark string with a timestamp and vendor URL adds no decision-relevant information and dilutes the definition.

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?

A composite audit with five parameters and no output schema should indicate what the audit returns and how the optional metrics interact with the fetched profile. Neither is covered, leaving the agent unable to predict results or reason about the optional inputs.

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 each of the five parameters is already documented. The description adds nothing about whether the four optional engagement metrics override measured values or serve as inputs, which is the one ambiguity the schema does not resolve.

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: 'Creator profile audit' combining 'bio-link page audit + engagement benchmark'. That composite scope implicitly separates it from single-purpose siblings like caelara_social_bio_link_auditor and caelara_social_engagement_rate_calc, though none are named.

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 composite over the narrower bio-link auditor or engagement-rate calculator, and no prerequisites or exclusions. The agent must infer that this is the bundled option from the word 'audit' alone.

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