facebook_post_getGet a Facebook post or Reel by URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public permalink to the Facebook post or reel. | |
| includeComments | No | When true, includes a sample of top-level comments when available. | |
| includeTranscript | No | When true, includes a plain-text transcript when available for the video. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, so the description does not contradict them. However, the description adds no behavioral details beyond the action itself—it does not mention what the response contains, any authentication requirements, or rate limits. With the annotations covering the read-only nature, the description provides minimal extra value but is consistent with the structured metadata.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words. It is appropriately brief for a simple get operation and does not attempt to restate the schema. It could optionally include a sentence about the response format, but the current length is efficient and focused.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, and the description does not indicate what the returned object will contain (e.g., post text, media, timestamps). While the tool is simple and the schema is descriptive, the absence of any return-value guidance or distinction from sibling tools leaves an agent uncertain about the output. Given the lack of output schema, the description should have at least mentioned that the result includes the post/reel content, but it only states the action.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 100% description coverage for the three parameters (url, includeComments, includeTranscript), each with a clear explanation. The tool description adds nothing beyond what the schema already conveys. Since the schema fully documents the parameters, the description does not need to repeat them, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (get) and the resource (Facebook post or Reel) with the input being a URL. It is not a tautology, and it distinguishes the tool from other Facebook getters like facebook_event_get or facebook_group_get, though it doesn't explicitly contrast them. The phrasing 'get a post or reel by URL' is specific enough for an agent to understand the primary purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as facebook_post_comments_list or facebook_post_transcript_get. There are no use-case hints, no exclusions, and no mention of alternative tools that might be preferred under different conditions. An agent is left to infer the appropriate context solely from the tool name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.