Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Meta pages & ad accounts

list_meta_pages
Read-onlyIdempotent

Lists Facebook Pages, linked Instagram business accounts, and ad accounts on your connected Meta account so you can choose targets before posting or creating campaigns.

Instructions

List the Facebook Pages (with any linked Instagram business account) and ad accounts on the connected Meta account — use before post_to_meta / create_meta_campaign to pick the target. Requires the user to have connected Meta (Settings > Connectors > Meta); returns a connect hint if not.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "adAccounts": {
-      "items": {},
-      "type": "array"
-    },
-    "pages": {
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.15

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the stateless-read profile is covered structurally. The description adds genuinely non-derivable behavior: the connector prerequisite and the fact that the tool returns a connect hint rather than erroring when Meta is not connected. It does not cover pagination or result shape, keeping it short of a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with what is listed, then the when-to-use routing, then the prerequisite. Every clause carries information an agent needs and nothing is repeated from the title or annotations.

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?

With no output schema and no parameters, this is exactly the scope an agent needs: what comes back, when to call it, what it feeds into, and what happens on the failure path when Meta is not connected. No material gap remains for a zero-arg enumeration tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is no schema semantics for the description to supplement. It does usefully characterize the payload (Pages plus linked Instagram accounts, plus ad accounts), which is the closest analogue to parameter selection for a no-arg list tool.

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 precise verb+resource ('List the Facebook Pages ... and ad accounts on the connected Meta account') and disambiguates from near-neighbors in a crowded sibling list (list_meta_posts, list_linkedin_pages, list_pinterest_boards) by naming Meta specifically. It also goes beyond the title by clarifying that linked Instagram business accounts are folded into the Page entries.

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 says when to use it ('use before post_to_meta / create_meta_campaign to pick the target'), which names both the downstream alternatives and the decision it feeds. It also states the precondition the agent cannot infer: the user must have connected Meta via Settings > Connectors > Meta.

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

Deploy Server

Other Tools