Page Lemon

Read the activity log

get_activity

Read-onlyIdempotent

Returns the activity log, newest first: who did what (publishing, rollbacks, people, domains, settings, protection, visitor data, AI apps, billing), where and when. Personal account (paid plans), or a workspace: Owner all, Admin all but billing, others their own.

Input Schema

Name	Required	Description
`site`	No
`type`	No
`limit`	No	Default 50
`before`	No	next_before from the last call
`person`	No	Email or id
`workspace`	No	Workspace id or name (default: own account)

Output Schema

Name	Required	Description	Default
`entries`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / workspace / description

Previous value: -"Workspace id or name; leave out for the person's own account"New value: +"Workspace id or name (default: own account)"

Changed3 schema fields changedOct 25, 2026

removedInput schema / properties / site / description
```
Removed value: -"Site name"
```
removedInput schema / properties / type / description
```
Removed value: -"Kind of action"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "entries": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedOct 21, 2026

removedInput schema / properties / limit / maximum
```
Removed value: -100
```
removedInput schema / properties / person / maxLength
```
Removed value: -320
```
removedInput schema / properties / site / maxLength
```
Removed value: -100
```
removedInput schema / properties / workspace / maxLength
```
Removed value: -100
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": {},
-  "properties": {
-    "agent_message": {
-      "type": "string"
-    },
-    "confirm_token": {
-      "type": "string"
-    },
-    "error": {
-      "description": "On failure (isError): {code, message}"
-    }
-  },
-  "type": "object"
-}New value: +null

AddedOct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description adds real context beyond them: newest-first ordering and role-based visibility (Owner sees all, Admin all but billing, others only their own) plus the paid-plan prerequisite.

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 dense, front-loaded sentences with no filler; the scope/permission detail follows the core purpose. Slightly compressed ('who did what ... where and when') but readable.

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 read-only log tool with annotations and an output schema, the description supplies the key non-schema facts: ordering, event categories, and per-role visibility. Remaining gaps (site/person filter semantics) are covered by the schema.

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 67% with an output schema present. The description usefully maps the `type` enum categories (publishing, rollbacks, people, domains, settings, protection, visitor data, AI apps, billing) and the newest-first ordering clarifies how `before` pagination works, adding meaning 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?

States a specific verb+resource ('Returns the activity log') and enumerates the event categories it covers, so an agent knows this is the audit/event feed rather than analytics. No explicit distinction from siblings like get_analytics, keeping it below 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?

The description explains access scoping (personal paid account vs. workspace roles) which implies when results differ, but it gives no explicit when-to-use-this-vs-alternatives guidance or exclusions.

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

All Page Lemon tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?