Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_social_tiktok_oembed

Retrieve TikTok video metadata from a URL via public oEmbed for social analytics, enabling title, author, and embed details to be fetched without scraping.

Instructions

[Social Analytics] TikTok video metadata via public oEmbed 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_tiktok_oembed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTikTok video URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute real operational context: measured p50 12 ms / p95 14 ms latency with a dated benchmark source, plus the underlying endpoint host, which signals a fast, unauthenticated public read. It says nothing about failure modes for private/deleted/region-blocked videos, rate limits, or what the response contains, leaving the mutation-free read semantics only implicit.

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 short sentences with the purpose front-loaded and no redundant restatement of the name. The benchmark timestamp and domain reference are slightly promotional overhead but still carry usable latency information.

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 annotations, the definition covers purpose, mechanism, and speed adequately. However, with no output schema, it should describe the shape of the returned oEmbed payload (title, author, thumbnail, dimensions) so an agent knows what it gets back.

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 coverage is 100% for the single required 'url' parameter, so the baseline is 3. The description adds only the platform qualifier ('TikTok video URL'), which is already implied by the tool name and schema, and does not specify accepted URL forms (e.g. short vm.tiktok.com links vs canonical video URLs).

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 states a specific verb+resource combination — 'TikTok video metadata via public oEmbed' — which tells an agent exactly what is retrieved and by what mechanism, and the TikTok scope implicitly separates it from the YouTube metadata sibling. It stops short of an explicit sibling contrast, so it lands at clear-but-not-differentiating.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of when to prefer the YouTube metadata sibling or the video viral audit composite, and no prerequisites stated. Usage is only implied by the single-purpose nature of the name and the 'public oEmbed' qualifier.

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