facebook_adLibrary_ad_getGet a single Facebook Ad Library ad by archive id or public Ad Library URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Public Facebook Ad Library URL for the ad. | |
| adId | No | Facebook Ad Library archive id for the ad. | |
| trim | No | When true, requests a smaller payload before normalization. | |
| includeTranscript | No | When true, includes a plain-text transcript when available for the ad video. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the read-only and external-data nature. The description adds little beyond the fact that it retrieves a single ad. It does not mention potential failure modes, normalization, or the effect of 'trim' and 'includeTranscript' in detail, but given the annotations, the bar is lower and a 3 is appropriate.
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, concise sentence that front-loads the core purpose. It contains no redundant or distracting information, making it efficient for an agent to parse.
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?
For a straightforward single-ad retrieval tool with no output schema, the description is mostly complete. It does not explicitly state what happens if the ad is not found or describe the return shape, but given the openWorldHint and the simplicity, this is a minor gap. The optional parameters are self-explanatory via the schema.
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?
Schema coverage is 100%, so all four parameters are documented. The description clarifies that url and adId are alternative locators, which adds a tiny bit of meaning beyond the schema. However, it adds no new information about 'trim' or 'includeTranscript' beyond their schema descriptions, so a baseline 3 is suitable.
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 tool retrieves a single Facebook Ad Library ad using either an archive id or public URL. This directly distinguishes it from search and list tools in the same domain, such as facebook_adLibrary_ads_search_get or facebook_company_ads_list.
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?
By specifying retrieval 'by archive id or public Ad Library URL', the description implies the tool is appropriate when the user has a specific ad identifier. It does not explicitly warn against using it for searching or list all ads, but the wording makes the usage context reasonably clear.
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.