Skip to main content
Glama

OmniSocials

by com.omnisocials.mcp
OverviewDiscussionsAdmin

search_locations

Read-only

Search for a location to tag on a post. Use this whenever the user wants to post WITH a place/location (e.g. "tag my dealership", "post this at the café"). It returns matching real venues with their addresses and a location ID.

Pick the platform with platform: "instagram" (default) or "threads". The two use DIFFERENT ids (a Facebook Place ID is not a Threads location id), so search with the platform you will tag. If the user wants both, search twice.

Flow (Instagram): call with the place name → present the options → once the user picks, pass that result's id as the top-level location_id on create_post / create_and_publish_post / update_post. Flow (Threads): same, but pass the id as threads.location_id. On a multi-post thread the tag goes on the first post.

Notes: use a SPECIFIC venue name (a broad brand like "Starbucks" returns individual store locations). Instagram: if the user already has a numeric Facebook Place ID, you can pass it straight to create_post; it's validated at publish and a bad one returns a clear error. If results are empty with a permission note, the workspace's Facebook app can't search arbitrary places — tell the user to use their own business Page's ID. Threads: needs the workspace's Threads connection to have the location permission; if the result says to reconnect Threads, tell the user to reconnect it under Settings → Organisation → Workspaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPlace name to search (min 2 chars) — a dealership, café, venue, etc.
platformNoWhich platform the location will be tagged on. Defaults to instagram. Use threads to get a Threads location id for threads.location_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover safety (readOnlyHint, openWorldHint, destructiveHint), and the description goes further by disclosing failure modes: empty results with a permission note mean the Facebook app can't search arbitrary places, Threads needs a location permission that may require reconnecting, and bad Place IDs are validated at publish. It stops short of describing pagination or result limits, but the behavioral context is rich.

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?

Well front-loaded (purpose, then platform choice, then per-platform flows, then edge-case notes) and every paragraph carries actionable content. It is long, but the density is justified by the multi-step tagging workflow it has to support.

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?

No output schema exists, so the description carries the return burden and does so ("matching real venues with their addresses and a location ID"), plus error/permission paths and the handoff to post-creation tools. Nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond it: the two platforms return DIFFERENT id namespaces, so you must search with the platform you'll tag, and it advises using a specific venue name since a broad brand returns individual stores.

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 ("Search for a location to tag on a post") and its role in a larger flow, clearly distinct from siblings like search_instagram_audio. An agent knows exactly what it does without opening the 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 trigger conditions ("whenever the user wants to post WITH a place/location") plus worked examples, then spells out the per-platform flow and how the returned id feeds create_post / create_and_publish_post / update_post. Alternatives and follow-up routing are unambiguous.

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

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