Skip to main content
Glama
Sign In

ReachSocial - One API for social media data.

by dev.reachsocial
OverviewDiscussionsAdmin

TikTok Profile Videos

tiktok_feed
Idempotent

Retrieve a normalized, cursor-paginated public TikTok profile feed. Use for a bounded list from one account/channel. For one specific post/video URL, use tiktok_video. Pass next_cursor back as cursor to request another page. An entitled B2B API key executes immediately under the client's billing and spending limits. OAuth requires an approved owner wallet connection and creates a $0.05 USDC payment request on Base; execution waits for browser approval/payment. Then use get_reachsocial_request with the returned request_id. Preserve the idempotency_key for retries; changed input needs a new key. Invalid/private/unavailable targets and access, rate, or spend limits return errors.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical TikTok profile URL. Supply a full https:// URL, not a handle or search query.
cursorNoOpaque provider-neutral pagination cursor. Omit for the first page; copy next_cursor from the prior result for a new page with a new idempotency_key.
max_itemsNoMaximum videos to return.
idempotency_keyYesThe calling agent/client generates this key automatically; do not ask the user to invent it. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it with the exact inputs before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page.

Output Schema

NameRequiredDescriptionDefault
dataNoDirect B2B normalized profile, item, or items; feeds may include next_cursor and has_more.
metaNoDirect B2B schema/normalization versions, response shape, and latency.
cachedNoWhether a direct B2B response reused cached normalized data.
resultNoStored execution response after OAuth payment; contains normalized data or a terminal failure.
statusYesB2B success or the current OAuth payment/execution state.
messageNoAction or recovery guidance for the current request state.
serviceYesCatalog service ID, such as instagram.profile.
request_idYesStored request identifier; preserve it for recovery.
payment_urlNoOwner browser link for USDC payment approval; present when payment is required.
price_centsNoOAuth request price in USD cents.
transactionNoSettled payment transaction identifier, when available.
payment_statusNoStored settlement state; uncertainty requires retrieval, never a new payment.
payment_endpointNoOwner-only acceptance endpoint, present only during an explicitly enabled validation run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Stable key for this logical request. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."New value: +"The calling agent/client generates this key automatically; do not ask the user to invent it. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it with the exact inputs before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."
  2. Changed16 schema fields changed
    • changedInput schema / properties / cursor / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 2048,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque provider-neutral pagination cursor. Omit for the first page; copy next_cursor from the prior result for a new page with a new idempotency_key."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Stable key for this logical request. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."
    • addedInput schema / properties / idempotency_key / maxLength
      Added value: +255
    • addedInput schema / properties / idempotency_key / minLength
      Added value: +1
    • changedInput schema / properties / max_items / default
      Previous value: -20New value: +12
    • addedInput schema / properties / max_items / description
      Added value: +"Maximum videos to return."
    • addedInput schema / properties / max_items / maximum
      Added value: +30
    • addedInput schema / properties / max_items / minimum
      Added value: +1
    • addedInput schema / properties / url / description
      Added value: +"Canonical TikTok profile URL. Supply a full https:// URL, not a handle or search query."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / maxLength
      Added value: +2048
    • addedOutput schema / description
      Added value: +"A B2B execution result or an OAuth request awaiting browser payment."
    • addedOutput schema / properties
      Added value: +{
+  "cached": {
+    "description": "Whether a direct B2B response reused cached normalized data.",
+    "title": "Cached",
+    "type": "boolean"
+  },
+  "data": {
+    "additionalProperties": true,
+    "description": "Direct B2B normalized profile, item, or items; feeds may include next_cursor and has_more.",
+    "title": "Data",
+    "type": "object"
+  },
+  "message": {
+    "description": "Action or recovery guidance for the current request state.",
+    "title": "Message",
+    "type": "string"
+  },
+  "meta": {
+    "additionalProperties": true,
+    "description": "Direct B2B schema/normalization versions, response shape, and latency.",
+    "title": "Meta",
+    "type": "object"
+  },
+  "payment_endpoint": {
+    "description": "Owner-only acceptance endpoint, present only during an explicitly enabled validation run.",
+    "title": "Payment Endpoint",
+    "type": "string"
+  },
+  "payment_status": {
+    "description": "Stored settlement state; uncertainty requires retrieval, never a new payment.",
+    "title": "Payment Status",
+    "type": "string"
+  },
+  "payment_url": {
+    "description": "Owner browser link for USDC payment approval; present when payment is required.",
+    "title": "Payment Url",
+    "type": "string"
+  },
+  "price_cents": {
+    "description": "OAuth request price in USD cents.",
+    "title": "Price Cents",
+    "type": "integer"
+  },
+  "request_id": {
+    "description": "Stored request identifier; preserve it for recovery.",
+    "title": "Request Id",
+    "type": "string"
+  },
+  "result": {
+    "additionalProperties": true,
+    "description": "Stored execution response after OAuth payment; contains normalized data or a terminal failure.",
+    "title": "Result",
+    "type": "object"
+  },
+  "service": {
+    "description": "Catalog service ID, such as instagram.profile.",
+    "title": "Service",
+    "type": "string"
+  },
+  "status": {
+    "description": "B2B success or the current OAuth payment/execution state.",
+    "enum": [
+      "success",
+      "payment_required",
+      "awaiting_approval",
+      "reconciliation_required",
+      "succeeded",
+      "failed",
+      "expired"
+    ],
+    "title": "Status",
+    "type": "string"
+  },
+  "transaction": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "Settled payment transaction identifier, when available.",
+    "title": "Transaction"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "request_id",
+  "service",
+  "status"
+]
    • changedOutput schema / title
      Previous value: -"tiktok_feedDictOutput"New value: +"MCPServiceResult"
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already tell the agent this is open-world, idempotent, non-destructive, and NOT read-only; the description explains why readOnlyHint is false by disclosing the B2B billing path and the OAuth $0.05 USDC payment request that blocks execution until browser approval — genuinely additive context. It also discloses the failure surface (invalid/private targets, access/rate/spend limits) and idempotency-key reuse semantics. The remaining gap is that it never says what a pending-payment response looks like versus a completed one, leaving the agent to infer the blocking behavior from the polling instruction.

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-loaded with purpose and sibling routing, then pagination, then billing/auth, then error cases — a sensible order where each sentence carries information. It reads as a dense run-on chain touching billing, pagination, idempotency, and errors in one block; a short structural break would aid scanning, but nothing is padding.

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?

An output schema exists, so return shape needn't be described; what the agent cannot get from structured fields — the async payment gate, the follow-up call to get_reachsocial_request, and the key-reuse rule for retries — is covered. For a dual-auth, potentially blocking tool, this is complete enough to invoke correctly.

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 four parameters are already documented, which sets the baseline at 3. The description restates the cursor chaining and idempotency-key rules ("changed input needs a new key") in slightly less detail than the schema itself, adding emphasis rather than new meaning.

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 verb+resource ("Retrieve a normalized, cursor-paginated public TikTok profile feed") with scope (one account/channel, bounded list) and explicitly names tiktok_video as the tool for a single post URL. An agent can distinguish it from the video and profile siblings without opening a schema.

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?

Gives explicit when-to-use (bounded list from one account) and when-not (single post/video URL → tiktok_video), plus the pagination loop (pass next_cursor as cursor) and the post-execution handoff to get_reachsocial_request with the returned request_id. Retry/idempotency rules and error conditions are spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ReachSocial - One API for social media data. toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources