Skip to main content
Glama

Facebook: Search

facebook_search
Read-only

Search Facebook by keyword: pages, people, posts, videos and locations.

Actions:

  • action=pages: Find Facebook pages by keyword (brand, business or topic name), optionally near a location. Returns page names, URLs, categories and follower counts, 3 per call, plus an end_cursor. Use it when you don't have the page URL; then call facebook_page (action=details) with a result's URL. For locations, get a location_uid from action=locations. Pricing: 1 credit per call. Inputs: query (required), location_uid (optional), end_cursor (optional).

  • action=people: Find public Facebook profiles by name or keyword, optionally near a location (location_uid from action=locations). Returns names, profile URLs and pictures, plus work, education and location where public, and an end_cursor. Pricing: 1 credit per call. Inputs: query (required), location_uid (optional), end_cursor (optional).

  • action=posts: Search public Facebook posts by keyword, optionally filtered by location (location_uid from action=locations) and date range. Returns posts with text, author and engagement, plus an end_cursor. To list one page's posts, use facebook_page (action=posts) instead. Pricing: 1 credit per call. Inputs: query (required), location_uid (optional), start_time (optional), end_time (optional), recent_posts (optional), end_cursor (optional).

  • action=videos: Search public Facebook videos by keyword, optionally most recent first or live videos only. Returns video titles, URLs and view counts, plus an end_cursor. Pricing: 1 credit per call. Inputs: query (required), most_recent (optional), videos_live (optional), fields (optional), end_cursor (optional).

  • action=locations: Look up Facebook places by name (city, region, venue) and get their location_uid. The location_uid is only used to filter action=pages, action=people and action=posts; it is not a Marketplace location (use facebook_marketplace (action=city_coordinates) for that). Pricing: 1 credit per call. Inputs: query (required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch keyword. pages: a brand or business name · people: a name · posts, videos: words in the text · locations: a city, place or landmark. Required for: pages, people, posts, videos, locations.
actionYesWhich operation to run. See the tool description for what each action returns and which parameters it needs.
fieldsNoComma-separated list of response fields to include. Optional for: videos.
end_timeNoFilter posts before this date (YYYY-MM-DD). Optional for: posts.
end_cursorNoPagination cursor. Optional for: pages, people, posts, videos.
start_timeNoFilter posts after this date (YYYY-MM-DD). Optional for: posts.
most_recentNoWhen "true", shows most recent videos first. Optional for: videos.
videos_liveNoWhen "true", filters for live videos only. Optional for: videos.
location_uidNoLocation UID from action=locations, to limit results to a place. Optional for: pages, people, posts.
recent_postsNoWhen "true", shows only recent posts. Optional for: posts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesJSON response from the SocialAPIs REST endpoint, unchanged. Object or array depending on the endpoint; most include a `meta` block (statusCode, duration, creditsCharged, creditsRemaining).
creditsChargedNoCredits charged for this call, or null if the endpoint did not report it.
creditsRemainingNoCredits left on the API key after this call, or null if not reported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / end_cursor / description
      Previous value: -"pages, people, posts, videos (optional): Pagination cursor."New value: +"Pagination cursor.\nOptional for: pages, people, posts, videos."
    • changedInput schema / properties / end_time / description
      Previous value: -"posts (optional): Filter posts before this date (YYYY-MM-DD)."New value: +"Filter posts before this date (YYYY-MM-DD).\nOptional for: posts."
    • changedInput schema / properties / fields / description
      Previous value: -"videos (optional): Comma-separated list of response fields to include."New value: +"Comma-separated list of response fields to include.\nOptional for: videos."
    • changedInput schema / properties / location_uid / description
      Previous value: -"pages (optional): Location UID for filtering (from search/locations endpoint). people, posts (optional): Location UID for filtering."New value: +"Location UID from action=locations, to limit results to a place.\nOptional for: pages, people, posts."
    • changedInput schema / properties / most_recent / description
      Previous value: -"videos (optional): When \"true\", shows most recent videos first."New value: +"When \"true\", shows most recent videos first.\nOptional for: videos."
    • changedInput schema / properties / query / description
      Previous value: -"pages (required): Keyword to search for, e.g. a brand or business name. people (required): Name or keyword to search for. posts (required): Keyword or phrase to search post text for. videos (required): Keyword or phrase to search videos for. locations (required): Search query (city, place, landmark)."New value: +"Search keyword. pages: a brand or business name · people: a name · posts, videos: words in the text · locations: a city, place or landmark.\nRequired for: pages, people, posts, videos, locations."
    • changedInput schema / properties / recent_posts / description
      Previous value: -"posts (optional): When \"true\", shows only recent posts."New value: +"When \"true\", shows only recent posts.\nOptional for: posts."
    • changedInput schema / properties / start_time / description
      Previous value: -"posts (optional): Filter posts after this date (YYYY-MM-DD)."New value: +"Filter posts after this date (YYYY-MM-DD).\nOptional for: posts."
    • changedInput schema / properties / videos_live / description
      Previous value: -"videos (optional): When \"true\", filters for live videos only."New value: +"When \"true\", filters for live videos only.\nOptional for: videos."
  2. Changed9 schema fields changed
    • changedInput schema / properties / end_cursor / description
      Previous value: -"For pages, people, posts, videos: Pagination cursor."New value: +"pages, people, posts, videos (optional): Pagination cursor."
    • changedInput schema / properties / end_time / description
      Previous value: -"For posts: Filter posts before this date (YYYY-MM-DD)."New value: +"posts (optional): Filter posts before this date (YYYY-MM-DD)."
    • changedInput schema / properties / fields / description
      Previous value: -"For videos: Comma-separated list of response fields to include."New value: +"videos (optional): Comma-separated list of response fields to include."
    • changedInput schema / properties / location_uid / description
      Previous value: -"For pages: Location UID for filtering (from search/locations endpoint). For people, posts: Location UID for filtering."New value: +"pages (optional): Location UID for filtering (from search/locations endpoint). people, posts (optional): Location UID for filtering."
    • changedInput schema / properties / most_recent / description
      Previous value: -"For videos: When \"true\", shows most recent videos first."New value: +"videos (optional): When \"true\", shows most recent videos first."
    • changedInput schema / properties / query / description
      Previous value: -"For pages: Keyword to search for, e.g. a brand or business name. For people: Name or keyword to search for. For posts: Keyword or phrase to search post text for. For videos: Keyword or phrase to search videos for. For locations: Search query (city, place, landmark)."New value: +"pages (required): Keyword to search for, e.g. a brand or business name. people (required): Name or keyword to search for. posts (required): Keyword or phrase to search post text for. videos (required): Keyword or phrase to search videos for. locations (required): Search query (city, place, landmark)."
    • changedInput schema / properties / recent_posts / description
      Previous value: -"For posts: When \"true\", shows only recent posts."New value: +"posts (optional): When \"true\", shows only recent posts."
    • changedInput schema / properties / start_time / description
      Previous value: -"For posts: Filter posts after this date (YYYY-MM-DD)."New value: +"posts (optional): Filter posts after this date (YYYY-MM-DD)."
    • changedInput schema / properties / videos_live / description
      Previous value: -"For videos: When \"true\", filters for live videos only."New value: +"videos (optional): When \"true\", filters for live videos only."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only/open-world/destructive profile, yet the description adds substantial context beyond them: per-call credit pricing for every action, pagination via end_cursor, the fields each action returns, and the constraint that location_uid only filters pages/people/posts. This is rich, specific behavioral disclosure.

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?

Front-loaded with the resource list, then structured per action with returns and inputs, which is easy to scan. It loses a point for repeating boilerplate ('Pricing: 1 credit per call' and the input lists) on every action, some of which duplicates the schema.

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?

For a 10-parameter multi-action tool, the description covers every action's purpose, applicable parameters, return shape, pagination, cost, and cross-tool routing. With annotations and an output schema also present, nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents every parameter, including per-action applicability. The description's per-action 'Inputs' lists largely restate what the schema states, so it adds only marginal semantic value over structured data.

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?

The description states a specific verb (search) and resource (Facebook: pages, people, posts, videos, locations) and enumerates each sub-operation with its own return payload. It clearly distinguishes itself from siblings by naming facebook_page and facebook_marketplace as the tools for adjacent jobs.

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?

Routing is explicit and conditional: use facebook_page (action=details) if you lack a page URL, use facebook_page (action=posts) to list one page's posts, and use facebook_marketplace (action=city_coordinates) for Marketplace locations. It also states how actions chain (get location_uid from action=locations first).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.