Page Lemon

Get sites and plan

get_account

Read-onlyIdempotent

Returns the signed-in account: plan, workspaces, sites (20 at a time, searchable), notices, new-item counts, programs (student, startup).

Input Schema

Name	Required	Description
`include`	No	Any of: billing, usage, storage, downgrade, notifications, all. Extra sections
`sites_limit`	No	Sites per call (default 20)
`sites_query`	No	Filter by name, title or workspace
`sites_cursor`	No	next_sites_cursor from the last call

Output Schema

Name	Required	Description	Default
`new`	No
`sites`	No
`notices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedInput schema / properties / include / description

Previous value: -"Any of: billing, usage, storage, downgrade, notifications, referrals, all. Extra sections (\"all\": every one but referrals). referrals: the person's own invite link and seats left, only when they ask for it; never suggest it"New value: +"Any of: billing, usage, storage, downgrade, notifications, all. Extra sections"

changedInput schema / properties / sites_query / description

Previous value: -"Only sites whose name, title or workspace contains this"New value: +"Filter by name, title or workspace"

Changed3 schema fields changedOct 25, 2026

changedInput schema / properties / include / description

Previous value: -"Extra sections (\"all\": every one but referrals). referrals: the person's own invite link and seats left, only when they ask for it; never suggest it"New value: +"Any of: billing, usage, storage, downgrade, notifications, referrals, all. Extra sections (\"all\": every one but referrals). referrals: the person's own invite link and seats left, only when they ask for it; never suggest it"

removedInput schema / properties / include / items / enum

Removed value: -[
-  "billing",
-  "usage",
-  "storage",
-  "downgrade",
-  "notifications",
-  "referrals",
-  "all"
-]

removedOutput schema / properties / notices / items / properties
```
Removed value: -{}
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / include / description

Previous value: -"Extra sections (\"all\": every one but referrals). referrals: the person's own invite link (and invite seats left), only when they ask for it; never suggest it"New value: +"Extra sections (\"all\": every one but referrals). referrals: the person's own invite link and seats left, only when they ask for it; never suggest it"

Changed8 schema fields changedOct 22, 2026

removedOutput schema / properties / agent_message
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / confirm_token
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / error

Removed value: -{
-  "description": "On failure (isError): {code, message}"
-}

addedOutput schema / properties / new / additionalProperties
```
Added value: +{
+  "type": "number"
+}
```

removedOutput schema / properties / new / description

Removed value: -"Counts of new items needing attention, by kind"

removedOutput schema / properties / new / properties
```
Removed value: -{}
```

removedOutput schema / properties / notices / description

Removed value: -"Problems and unread notices (at most 10); mention a problem first; reading marks nothing"

addedOutput schema / properties / sites

Added value: +{
+  "items": {
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed5 schema fields changedOct 21, 2026
- removedInput schema / properties / sites_limit / maximum
```
Removed value: -100
```
- removedInput schema / properties / sites_query / maxLength
```
Removed value: -100
```
- removedOutput schema / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / new / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / notices / items / additionalProperties
```
Removed value: -{}
```

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / include / description

Previous value: -"Extra sections"New value: +"Extra sections (\"all\": every one but referrals). referrals: the person's own invite link (and invite seats left), only when they ask for it; never suggest it"

changedInput schema / properties / include / items / enum

Previous value: -[
-  "billing",
-  "usage",
-  "storage",
-  "downgrade",
-  "all"
-]New value: +[
+  "billing",
+  "usage",
+  "storage",
+  "downgrade",
+  "notifications",
+  "referrals",
+  "all"
+]

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / sites_query / description

Previous value: -"Only sites whose name or workspace contains this"New value: +"Only sites whose name, title or workspace contains this"

First observedOct 14, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds one genuinely new fact, that sites are returned 20 at a time and are searchable, but says nothing about the cursor round-trip or what 'notices' and 'new-item counts' actually contain.

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?

One sentence, front-loaded with the verb and resource, with the payload list packed into parenthetical groups. No filler, though the comma-separated enumeration is dense and slightly hard to scan.

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?

With a rich output schema and full param coverage, the description does not need to explain return values, and it doesn't. What is missing is routing context, i.e. why an agent would pick this over the many narrower sibling getters, which matters for a tool whose payload overlaps several of them.

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%, documenting `include` values, `sites_limit` default 20, `sites_query` filter fields, and `sites_cursor`. The description's '20 at a time, searchable' merely restates the limit and query params without adding format or interaction detail, so the baseline 3 applies.

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 ('Returns the signed-in account') and enumerates the payload sections (plan, workspaces, sites, notices, counts, programs). It is clearly distinguishable from single-resource siblings like get_site or get_domains, though it never names those alternatives.

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 guidance on when to call this versus get_site, get_activity, or get_domains, and no signal about when the extra `include` sections are worth requesting. The agent must infer that this is the 'everything about my account' entry point.

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?