Skip to main content
Glama

Get Ai Publisher History

hgr_get_ai_publisher_history
Read-onlyIdempotent

Reads AI Publisher history for one visible store. 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>",
      "channelOAuthId": "<channelOAuthId>"
    },
    "name": "hgr_get_ai_publisher_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesWAPI AI Publisher history request body.
channelOAuthIdYesChannelOAuthId returned by hgr_list_channels for the selected visible store.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a useful auth note about the HGRApi Header channel, but the clause 'ChannelOAuthId resolved internally' sits awkwardly against a schema that marks channelOAuthId as a required caller-supplied parameter, creating mild confusion about who supplies it.

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?

Two short sentences with the operation and scope front-loaded; there is no filler. The second sentence is the weakest part, since its auth clause is partially redundant with the schema and partially inconsistent with it.

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 exists and annotations cover the read-only profile, so return values and safety need no prose. Still, the description never says what the history records represent or how far back they go, and the 'resolved internally' note muddies rather than clarifies parameter sourcing.

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 both parameters are already documented in the schema (including that ChannelOAuthId comes from hgr_list_channels). The description adds no meaning beyond that baseline and does not clarify what the 'body' request payload should contain.

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 and resource ('Reads AI Publisher history') plus scope ('for one visible store'), which separates it from siblings like hgr_get_ai_publisher_filters, hgr_change_ai_publisher_status, and hgr_update_ai_publisher_optimization. What 'history' actually contains is left unexplained, keeping it 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 Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no naming of the adjacent AI Publisher tools an agent might confuse this with (filters, status change, optimization update). The phrase 'for one visible store' hints at a preconditions step but does not spell one out.

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.