Skip to main content
Glama
Hermoso

Hermoso

Official

Fetch social data

fetch_social_data

Retrieve raw data from allowlisted social and web endpoints not covered by dedicated search tools. Use for long-tail queries across TikTok, Instagram, YouTube, Reddit, LinkedIn, and more.

Instructions

Generic escape hatch for any ALLOWLISTED long-tail social/web endpoint the dedicated search_* tools don't cover — e.g. {path:'/v1/instagram/profile', params:{handle:'nike'}}. Allowlisted platform families: TikTok (+ TikTok Shop), Instagram, YouTube, Facebook (organic profiles/posts/events/marketplace), LinkedIn (organic posts/companies), Twitter/X, Reddit, Threads, Snapchat, Pinterest, Twitch, Bluesky, Truth Social, Rumble, Spotify, SoundCloud, GitHub, Google search, link-in-bio pages (Linktree etc.). Param names vary per endpoint (profiles use handle, keyword searches use query, Reddit uses subreddit). WARNING: returns RAW provider JSON — large and messy; prefer the dedicated search_* tools. Spends credits.

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": {
      "path": "<path>"
    },
    "name": "fetch_social_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesexact endpoint path, e.g. '/v1/tiktok/profile' — non-allowlisted paths are rejected
paramsNoendpoint query params, e.g. {handle:'nike'}
get_costNotrue: return the price only; nothing runs or bills
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
  2. Addedv0.1.162

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: it spends credits, returns raw large/messy provider JSON, and rejects non-allowlisted paths. Annotations cover open-world and non-read-only semantics but say nothing about cost or output shape, so the description carries real weight here. It stops short of retry/rate-limit behavior, which keeps it at 4 rather than 5.

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?

Front-loads purpose, then example, then allowlist, then the warning — a sensible priority order with no filler sentences. The platform-family enumeration is long but functional, since it defines the allowlist boundary the agent must respect.

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

Completeness5/5

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

With no output schema, the description correctly discloses the return value (raw provider JSON, large and messy). For a five-param tool with a free-form nested params object, it supplies both the variability warning and concrete examples, which is everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description exceeds that by explaining that param names vary per endpoint (handle for profiles, query for keyword search, subreddit for Reddit), which the empty additionalProperties object cannot convey. It also frames path as endpoint-specific, matching the schema's allowlist note.

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

Purpose5/5

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

States a specific role — a generic escape hatch to allowlisted long-tail social/web endpoints — and concretely distinguishes itself from the dedicated search_* tools. The inline example call ({path:'/v1/instagram/profile', params:{handle:'nike'}}) makes the shape of the invocation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use: only for endpoints the dedicated search_* tools don't cover. Explicit preference rule: 'prefer the dedicated search_* tools' is stated twice, once as a WARNING. Boundary conditions (non-allowlisted paths rejected) are also given.

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