Skip to main content
Glama

List Business Facebook Businesses

list_community_facebook_businesses
Read-only

List Facebook businesses available to the provided Facebook access token. Business and community refer to the same thing and are interchangeable. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "facebookAccessToken": "<facebookAccessToken>"
    },
    "name": "list_community_facebook_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
facebookAccessTokenYesFacebook user access token from the Facebook login step.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / facebookAccessToken / description
      Added value: +"Facebook user access token from the Facebook login step."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds access-gating behavior the annotations cannot express: plan-tier blocking, permission pre-checks, grace-period warnings, and a stop condition when access is blocked. It does not say what the response contains or how many businesses are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, but the remainder is a procedural policy block with redundancy: permission checking is stated twice ('Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs'). The aliasing sentence is useful; the duplicated gate instructions are not.

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?

For a two-parameter read-only list tool with full schema coverage and no output schema, the definition covers purpose, prerequisites, and blocking conditions. The main remaining gap is the shape of the returned list, which an agent must discover at call time.

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 100% and both parameters carry descriptions, including the warning not to invent communityId. The description adds only the framing that 'business and community refer to the same thing', which is a real clarification of the ID semantics but does not go beyond that baseline.

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?

States a specific verb and resource: 'List Facebook businesses available to the provided Facebook access token.' An agent can tell what it retrieves. It does not distinguish itself from near-identical siblings such as list_business_facebook_businesses or the pixel-listing variants, leaving that differentiation to 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?

Explicitly routes the agent to check_business_tool_access before collecting inputs and before offering the action, and states a hard negative condition: FREE businesses cannot use this tool regardless of feature rows. It also specifies workflow behavior on grace-period warnings and blocked access, which is unusually prescriptive 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