Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

facebook_comments

Facebook post comments with reactionCount, reactions.like when mixed, author.id (pfbid), and replyCount. Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoFacebook post or Reel URL. Omit when feedbackId is set. The URL platform must match this endpoint's platform. A page/profile URL also works: Facebook renders the page's most recent post first, so you get that post's comments (each comment's url names the actual post).
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 50, max 500). Flat 2 credits per call.
feedbackIdNoPost feedback id from /v1/facebook/details (base64 feedback:POSTID). Prefer when you already have it — also accepts feedback_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Facebook post or Reel URL. Omit when feedbackId is set. The URL platform must match this endpoint's platform."New value: +"Facebook post or Reel URL. Omit when feedbackId is set. The URL platform must match this endpoint's platform. A page/profile URL also works: Facebook renders the page's most recent post first, so you get that post's comments (each comment's url names the actual post)."
  2. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  3. Changed4 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / feedbackId / description
      Previous value: -"Post feedback id from /v1/facebook/details. Prefer when you already have it."New value: +"Post feedback id from /v1/facebook/details (base64 feedback:POSTID). Prefer when you already have it — also accepts feedback_id."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 50, max 500. Flat 2 credits per call."New value: +"Max items to return (default 50, max 500). Flat 2 credits per call."
    • changedInput schema / properties / url / description
      Previous value: -"Facebook post or Reel URL. Omit when feedbackId is set."New value: +"Facebook post or Reel URL. Omit when feedbackId is set. The URL platform must match this endpoint's platform."
  4. Changed4 schema fields changed
    • addedInput schema / properties / feedbackId
      Added value: +{
+  "description": "Post feedback id from /v1/facebook/details. Prefer when you already have it.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 50, max 500. Billed per result."New value: +"Max items to return. Default 50, max 500. Flat 2 credits per call."
    • changedInput schema / properties / url / description
      Previous value: -"Public Facebook video or post URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"Facebook post or Reel URL. Omit when feedbackId is set."
    • removedInput schema / required
      Removed value: -[
-  "url"
-]
  5. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 50, max 500. Flat 2 credits per call."New value: +"Max items to return. Default 50, max 500. Billed per result."
  6. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 50, max 500. Billed per result."New value: +"Max items to return. Default 50, max 500. Flat 2 credits per call."
  7. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  8. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}
  9. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Public Facebook video or post URL."New value: +"Public Facebook video or post URL. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."
  10. First observed

TDQS

B3.3/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 does disclose meaningful behavioral traits: cost per call (2 credits), free on empty/failure, cache behavior (default fresh, 24h hit with cache=true), and the conditional presence of reactions.like ('when mixed'). However, it omits other behavioral details such as whether only top-level comments are returned, pagination behavior, auth requirements, or rate limits.

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

Conciseness5/5

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

The description is two compact sentences with no fluff; the first sentence front-loads the resource and key output fields, the second packs cost and cache behavior. Every clause earns its place and the wording is dense but readable.

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?

Given there is no output schema and no annotations, the description should clarify the response shape and usage scope, but it only lists a few fields and omits whether the result is an array, how pagination works, and the difference from comment replies. The schema enriches some context (URL can be a post or Reel, feedbackId from details), so it is adequate but not complete.

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%, with all four parameters (url, cache, limit, feedbackId) already documented in the input schema. The description mostly duplicates the cache behavior ('Pass cache=true') and adds cost/cache side effects, but offers no new parameter semantics beyond what the schema already states, so the baseline of 3 applies.

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 clearly identifies the resource as 'Facebook post comments' and enumerates the exact fields returned (reactionCount, reactions.like when mixed, author.id pfbid, replyCount), which makes the tool's function unambiguous. However, it lacks an explicit verb like 'retrieves' or 'lists' and does not distinguish itself from the sibling facebook_comment_replies within the description text itself.

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?

The description provides conditional guidance only for caching ('Pass cache=true for a free 24h cache hit') and cost behavior, not for tool selection. It never states when to use facebook_comments versus facebook_comment_replies, facebook_details, or other platform-comment tools like youtube_comments or tiktok_comments.

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

All captapi 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