Resolve a place name (city, region, or country) to Facebook location IDs. Use the returned id as the location_id argument to search_facebook_posts or search_facebook_events to scope a search to that place.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Place name to resolve, e.g. "London" or "Paris, France" (max 500 characters) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description is the only behavioral disclosure. It explains the output's purpose but does not mention handling of ambiguous names, multiple matching locations, no-result cases, or exact return format—important gaps for a resolver.
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?
Two sentences, purpose first, every word earns its place. It is brief and highly scannable.
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 single-parameter resolver, the description fully covers purpose, input scope, and output usage via downstream tool references. No output schema is needed when the description points to the exact consumers.
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 already defines 'query' with a description and max length. The description adds semantic narrowing by specifying accepted entity types (city, region, country), which is extra value beyond the schema.
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 uses a specific verb 'Resolve' and clearly states the resource (place name to Facebook location IDs). It distinguishes this from sibling content-search tools by framing it as a preparatory lookup step.
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?
Explicitly tells when to use the tool (to obtain a location ID for scoping searches) and names two direct consumer tools (search_facebook_posts, search_facebook_events). This provides clear integration context and implicitly contrasts with alternative search tools.
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.
Most tools are clearly scoped by platform and resource (e.g. search_twitter vs twitter_user_tweets vs twitter_tweet_details). A few pairs like twitter_tweet_comments vs twitter_user_replies or facebook_page_posts vs search_facebook_posts could cause minor confusion, but descriptions generally clarify the distinction.
The dominant pattern is snake_case with a platform_prefix_resource suffix, and search_* consistently marks search operations. Minor deviations include noun-style names like amazon_best_sellers and place_photos, and the odd get_ skill/comments tools, but the overall convention is predictable.
74 tools is far beyond the typical well-scoped MCP server, even for a multi-platform API aggregator. The breadth is justified by the many platforms covered, but an agent will face a very large action space, and this could reasonably be split into per-platform servers.
The server provides strong lifecycle coverage for its read-only domain: search, profile/details, posts, and engagement data across most platforms. Gaps exist for some platforms (e.g. no LinkedIn person profile, no Facebook event details, no Truth Social profile/search, no Reddit subreddit-specific tools), but the core workflows are well covered.
