Skip to main content
Glama

Actions recent

actions_recent
Read-onlyIdempotent

Recorded actions with ids, evidence, execution state, undo availability and 24 hour, 3 day and 7 day observations: the source for undoing or reporting changes. since and accountIds scope a day or a period and add each platform's own log, Meta's activity log or Google Ads' change history (the last 30 days Google keeps, with who changed what in Google Ads, Editor, scripts, rules or Google's auto-applied recommendations), as one report over every account; by keeps one person's changes: me (whoever connected the platform), others (everyone else) or a name, an email on Google. When the log cannot tell who the person is, the result names the people it holds, for a new call with by set to one of them. A change report's table carries its CSV and PDF as links signed for the connected person, valid for one hour. Without showTable it returns rows for citing relevant applied changes with their timing, without causal claims. Paginated with nextOffset over the same scope.

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": "actions_recent"
  }
}

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. Changed8 schema fields changed
    • addedInput schema / properties / input / properties / by
      Added value: +{
      +  "description": "Whose changes: me, others (all but me) or a name",
      +  "type": "string"
      +}
    • addedInput schema / properties / input / properties / campaignIds
      Added value: +{
      +  "items": {
      +    "maxLength": 30,
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • changedInput schema / properties / input / properties / limit / maximum
      Previous value: -10New value: +50
    • changedInput schema / properties / input / properties / showTable / description
      Previous value: -"Display the journal only when explicitly requested. Omit for performance diagnosis."New value: +"Only when the journal is asked for."
    • addedInput schema / properties / input / properties / side
      Added value: +{
      +  "enum": [
      +    "adrails",
      +    "meta"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / input / properties / since
      Added value: +{
      +  "description": "YYYY-MM-DD; with accountIds, adds Meta's or Google's log.",
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • addedInput schema / properties / input / properties / until
      Added value: +{
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • 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."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, yet the description adds real behavior: Google's log covers only the last 30 days, a change report's CSV and PDF links are signed for the connected person and expire in one hour, and ambiguous identities come back as a named list requiring a follow-up call. These are things an agent cannot learn from the annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is substantive but delivered as one enormous run-on sentence chain with colon-spliced clauses and mid-sentence parentheticals about Google's retention window. Purpose is front-loaded, but the reader must parse three dense sentences to extract pagination, link expiry, and the identity fallback.

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 a multi-source, paginated read tool with no output schema, the description covers return shape (rows without causal claims, a table on request with signed links), pagination via nextOffset over the same scope, and the identity-resolution loop. Gaps remain around the side parameter and the limit/offset caps, which the schema states only as bare constraints.

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% (baseline 3), and the description earns above baseline by explaining cross-parameter behavior the schema does not: since combined with accountIds triggers inclusion of Meta's or Google's own log as one report across accounts, and by accepts 'me', 'others', or a person's name/email on Google. It still says nothing about side, limit, offset, until, or campaignIds.

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 opening clause names a concrete resource and its payload: 'Recorded actions with ids, evidence, execution state, undo availability and 24 hour, 3 day and 7 day observations', and frames it as 'the source for undoing or reporting changes'. That is clear, but it never names or contrasts with the obvious sibling changes_review, leaving the agent to infer the split.

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?

Useful situational cues exist: 'since and accountIds scope a day or a period and add each platform's own log', 'by keeps one person's changes', and 'Without showTable it returns rows for citing relevant applied changes'. What's missing is any exclusion or named alternative — nothing tells the agent when to call changes_review or reports elsewhere instead.

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.