Skip to main content
Glama
hermoso-ai

Hermoso

Official

The brand’s Partnership Ads creators

list_meta_partnership_creators
Read-only

Verify Meta partnership ad eligibility: read ad-permission and tag-approval lists, see pending or canceled statuses, and check specific creators via ID or handle.

Instructions

The creators this brand has set up for PARTNERSHIP ADS — ads that run from a CREATOR’s handle instead of the brand’s, which is what a paid collaboration looks like in feed. TWO SEPARATE LISTS come back and NEITHER IMPLIES THE OTHER: the AD-PERMISSION list is whose content this brand may run as an advert, and the TAG-APPROVAL list is who may tag this brand as a paid partner on their own organic post. Adding a creator to one does nothing for the other, and that is the mistake that makes a partnership ad fail for a reason Meta’s error does not name. Every row carries the status Meta reports VERBATIM. Meta’s own wording on the wire is prose, not the enum its docs publish — measured 2026-08-25, a fresh request reads “Pending Approval” and a revoked one reads “Canceled” (Partnership Ads Hub calls the same two rows “Request sent” and “Inactive”). PENDING means the creator has not accepted yet and this brand cannot advertise their content until they do. REVOKING DOES NOT REMOVE THE ROW: Meta keeps it and flips the status, so read the status rather than the presence of a row. An unrecognised status is passed through as Meta’s own word, never blanked. A list that could not be READ says exactly that; it is never rendered as "this brand has no creators". THE TWO LISTS ANSWER DIFFERENTLY, and Meta is the reason: the ad-permission list can be ENUMERATED, and the tag-approval list CANNOT — Meta requires user_ids on that edge and returns "a list of approved creators, filtered by the user IDs provided", i.e. it CHECKS the people you name and cannot report the rest. So pass creatorIds to ask about specific creators; anyone already on the ad-permission list is checked for you, which is what makes "on one list but not the other" answerable in a single call. With nobody to check, the reply says Meta publishes no way to list that edge rather than reporting a failed read. Read-only, 0 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdNoFacebook Page id — omit when only one Page is connected. Both lists live on its linked Instagram account.
creatorIdsNocomma-separated NUMERIC Instagram account ids to CHECK against the TAG-APPROVAL list. Meta publishes no way to list that edge — `user_ids` is required on it and the response is filtered to exactly the ids given — so without this the reply says so instead of reporting a read that failed. Handles do not work here (Meta publishes no username form for this parameter); the ad-permission list is the one that takes a @handle. Creators already on the ad-permission list are checked automatically.
creatorUsernameNonarrow the AD-PERMISSION list to one creator handle. It does not affect the tag-approval list, which is addressed by numeric id only.
Behavior5/5

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

The description is exceptionally transparent: it discloses read-only behavior and zero credit cost (consistent with annotations), the non-removal of revoked rows, the verbatim status wording from Meta, the enumeration/check asymmetry, and how failed reads are reported. No contradictions with annotations.

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?

The description is long, but every sentence serves a purpose, and the key details (two lists, the mistake, status wording) are front-loaded. It could be slightly tightened, but the structure is logical and the verbosity is justified by the complexity of Meta's behavior.

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?

Covers all essential aspects: the two lists, how to query each, failure semantics, Meta's API limitations, credit cost, and error handling. An agent has everything needed to invoke the tool correctly and interpret results, even without an output schema.

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

Parameters5/5

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

Even though the schema already documents all three parameters at 100% coverage, the description adds crucial meaning to each: pageId's optionality, creatorIds' necessity for tag-approval checking, and creatorUsername's scope—plus the numeric-vs-handle distinction and automatic checking. This goes far beyond the schema.

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 the specific resource — the brand's Partnership Ads creators — and clearly defines the two distinct lists (ad-permission and tag-approval). It differentiates from related tools like manage_meta_partnership_creator, so an agent can immediately know what this tool enumerates without confusion.

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?

Provides explicit usage context, such as when to check specific creators, the difference between the two lists, and the common pitfall of assuming one list implies the other. It does not explicitly name alternative tools but the instructions are clear enough for an agent to decide when to invoke this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server