Skip to main content
Glama

Editor settings reference

editor_settings_reference
Read-onlyIdempotent

Returns every setting of the Meta campaign editor that launch_brief's metaSettings accepts, with its allowed values and format; tool=meta_edit, meta_audience_create or lead_form_create returns that tool's format instead. Read only.

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": {
      "input": "<input>"
    },
    "name": "editor_settings_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / input / properties / tool
      Added value: +{
      +  "maxLength": 60,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so "Read only." earns no credit as it merely restates them. Beyond that, the description usefully discloses that output is scoped by the tool value and that allowed values and formats are included, which is real behavioral context the annotations cannot convey.

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 dense sentence with the return content front-loaded, followed by the tool-scoping caveat and a two-word safety note. No filler, no restatement of the title, and the most important information arrives first.

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?

With no output schema, the description does the necessary work by stating that allowed values and formats are returned, and it covers the one undocumented parameter's effect. It stops short of noting size, ordering, or whether results are cached, which would fully close the loop for a reference-style read 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?

Schema coverage is 75% and the three documented parameters carry their own descriptions, but the tool parameter itself has no schema description — the description is the only place its effect (returning that tool's format instead) is explained. That is a genuine semantic addition over the structured fields.

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 specific verb and resource ("Returns every setting of the Meta campaign editor") and ties it to a concrete consumer ("launch_brief's metaSettings accepts"), so the agent knows exactly what comes back and why it matters. It also distinguishes the variant behavior when the optional tool parameter is supplied, separating it from the plain-reference case.

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?

Usage is only implied: the phrasing about launch_brief's metaSettings accepting these settings suggests calling this before building a launch brief, but the description never says "call this before launch_brief" or states any when-not-to-use condition. The tool= branch describes output variation rather than selection guidance, leaving the agent to infer the sequencing.

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.