Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

pages_find

Read-onlyIdempotent

Search managed Facebook Pages by name or username substring to return matching page IDs and names, avoiding a full account listing when you only need one page.

Instructions

Find a Page by name among the managed Pages Search the Pages the token manages by a case-insensitive substring of the Page name or username. Returns matching page ids and names. Cheaper than listing every Page when you only need one. Graph API: GET me/accounts (filtered locally).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "pages_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
access_tokenNoOptional Facebook Page access token for this call only. Use it when the token you hold is not the one this server was configured with, or when the configured token has expired. Takes effect for this call and nothing else. Also accepted as token or page_token.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world access, so the description's job is to add context — which it does by disclosing the underlying call ('GET me/accounts') and, importantly, that filtering happens locally rather than server-side, a real behavioral trait affecting result completeness. It does not say what happens when many pages match or how results are ordered.

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?

Four short sentences, front-loaded with the purpose and ending with the cheapest-to-parse implementation note. The opening is slightly run-on ('among the managed Pages Search the Pages...'), which momentarily reads as two merged clauses, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, and annotations carry the safety profile. What remains thin is the `limit` parameter and multi-match behavior, the one thing an agent must guess before calling on a token with many pages.

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 coverage is only 33%, and only access_token is documented in the schema. The description compensates for `query` by defining its matching rule (case-insensitive substring over name or username), which is genuine added meaning. `limit` is left unexplained in both places — no default behavior, no statement of whether matches are truncated.

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 and resource ('Find a Page by name') plus the matching semantics ('case-insensitive substring of the Page name or username') and the return shape ('matching page ids and names'). It also implicitly contrasts itself with full enumeration, so an agent can tell it apart from pages_list without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use rule: 'Cheaper than listing every Page when you only need one', which routes the agent away from bulk listing for single-page lookups. It stops short of naming the alternative tool explicitly or stating when-not to use it (e.g. ambiguous/multiple matches, paging through many pages).

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