Plainrouter

Get Meta creative library

get-creative-library

Read-onlyIdempotent

Return Meta image and video assets with the ads and last-30-day performance historically associated with each asset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-creative-library"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum assets requested per type; capped at 10 and the projection byte budget. Use pagination to continue.
`cursor`	No	Opaque Meta cursor returned by a previous call.
`ads_limit`	No	Associated ads per asset, also capped at 30 across the requested asset pages.
`account_id`	No	Advertising account ID. Required when the workspace has more than one active account.
`ads_cursor`	No	Continue associated ads using performance.next_cursor, keeping the asset page arguments.
`asset_type`	No	Limit results to images or videos. Defaults to all.	all
`workspace_id`	No	Workspace ID returned by list_workspaces. Required when this credential reaches multiple workspaces.
`performance_cursor`	No	Continue the provider performance scan using performance_pagination.next_cursor.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive safety, so the bar is lower. The description adds genuinely useful behavioral context: results are historical and scoped to a 30-day performance window, which is not in the annotations.

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?

A single front-loaded sentence with zero waste that conveys verb, resource, and the two key associations compactly.

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 an 8-parameter read tool with full schema coverage and no output schema, the description summarizes the core return shape (assets + ads + performance) well. Pagination and multi-account mechanics live in the schema, so completeness is good though it does not mention pagination at all in prose.

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 description coverage is 100% with rich per-parameter guidance, so the schema does the heavy lifting. The description adds no parameter-level meaning (pagination, cursors, account/workspace requirements are all schema-only), so baseline 3 is correct.

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 (Return) and resource (Meta image and video assets), plus the key differentiator of attached ads and last-30-day performance. It does not explicitly name which sibling to prefer, so it stops short of 5, but the scope is unambiguous.

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

Usage Guidelines3/5

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

The phrase 'historically associated with each asset' implies this is for browsing the creative library with past performance, but there is no explicit when-to-use, when-not, or comparison to siblings like launch.creatives.index or get_account_inventory. Usage is only inferable.

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

All Plainrouter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?