Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_thumbnail_analyzer

Analyze a social thumbnail image to check its format, dimensions, aspect ratio, and file size before publishing.

Instructions

[Social Analytics] Analyze a thumbnail image: format, dimensions, aspect ratio, size 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_thumbnail_analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesImage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses latency benchmarks (p50 12 ms, p95 14 ms) and the backing endpoint, which is useful, but says nothing about fetching remote URLs, failure behavior on non-image inputs, size limits, or that the operation is a non-destructive read.

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 core purpose is front-loaded and efficient, but the benchmark timestamp and the 'Calls https://social.caelaralabs.com' sentence add implementation noise without helping an agent decide or invoke. The latency figures could arguably aid timeout planning, so it is not pure waste.

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 read tool with no output schema, the description partially covers the return values by listing the measured attributes, which is helpful. However, it omits input constraints and error behavior, leaving gaps that matter given the absence of annotations.

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?

There is a single required parameter with 100% schema description coverage ('Image URL'), so the schema already supplies the meaning. The description adds no constraints on URL form, allowed schemes, or size limits beyond what the schema states.

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 uses a specific verb ('Analyze') plus resource ('thumbnail image') and enumerates the extracted attributes: format, dimensions, aspect ratio, size. It is clearly distinct from siblings like the card extractor or profile composite, though it does not explicitly name them.

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 or when-not-to-use guidance and no alternatives named, despite several image/card-related siblings. The only implied usage is that this analyzes thumbnails, which an agent must infer.

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