Skip to main content
Glama

lookup_facebook_ad_companies

Read-onlyIdempotent

Find Facebook Ad Library companies. Read-only; no charge.

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": "lookup_facebook_ad_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so 'Read-only' in the description is a restatement of structured data and earns no credit. 'No charge' is a genuine addition beyond the annotations (cost transparency relative to credit-consuming siblings like create_export_jobs and quote_export_jobs), but the description says nothing about result limits, pagination, or what 'companies' includes.

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?

Two short clauses, front-loaded with the purpose. Efficient, though the 'Read-only' half is redundant given the annotations, so not every word earns its place.

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

Completeness3/5

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

With no output schema and a single-parameter input, the definition is minimally sufficient for invocation, but it omits result shape, count limits, and match behavior. The 'no charge' note is the only differentiating behavior conveyed.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'query' parameter has only a length constraint, so the description must compensate — and it does not. It never explains what the query string matches (company name, page name, ad text, partial vs. exact) or whether it is required, which is the key ambiguity for this lookup.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Find Facebook Ad Library companies.' An agent can tell what the tool returns, but nothing distinguishes it from the sibling lookup_* tools (facebook_marketplace_locations, instagram_hashtags, instagram_locations) beyond the platform name embedded in the tool name itself.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or exclusions. The agent must infer from the name alone that this is the tool for resolving a company name to a Facebook Ad Library entity. The sibling set contains several near-identical lookup_ tools with no routing guidance.

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.

Resources