Skip to main content
Glama

Change Ai Publisher Status

hgr_change_ai_publisher_status
Destructive

Changes AI Publisher automation status for one visible store. Requires confirmed=true and impactConfirmed=true. Requires HGRApi Header channel / ChannelOAuthId resolved internally.

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": {
      "body": "<body>",
      "confirmed": "<confirmed>",
      "impactConfirmed": "<impactConfirmed>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_change_ai_publisher_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWAPI AI Publisher status body: Id, Status.
confirmedYesMust be true after the user explicitly requested or confirmed the exact action.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.
impactConfirmedYesMust be true after the user explicitly confirmed the concrete high-impact consequences.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as destructive, non-idempotent, and open-world, so the safety profile is largely covered. The description adds a valuable confirmation gate and notes internal channel resolution, but it does not explain what the status change actually does, what consequences are confirmed, or whether the change is reversible.

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 three short sentences and front-loads the core action before prerequisites. The phrase about the HGRApi Header channel and ChannelOAuthId is slightly cryptic, but overall there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema, rich annotations, and full schema coverage reduce the description's burden. Still, for a destructive status-change tool, it omits the concrete effect of the change and the high-impact consequences the user must confirm, leaving a meaningful gap.

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%, so parameter documentation is already strong. The description reiterates the confirmed/impactConfirmed requirements and mentions ChannelOAuthId resolution, but adds no semantics about valid AI Publisher status values or body contents beyond the schema.

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?

The description states a clear verb and resource: 'Changes AI Publisher automation status for one visible store.' The single-store scope is useful. It does not differentiate this tool from nearby siblings such as hgr_update_ai_publisher_optimization or hgr_create_ai_publisher_agent, so it falls short of a 5.

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?

It gives prerequisites ('Requires confirmed=true and impactConfirmed=true') and scope ('one visible store'), which implies when the tool is applicable. However, it never states when to use this tool instead of alternatives or when not to use it, so usage guidance remains implicit.

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