Ginta

The user's websites, plan and limits

list_sites

Read-onlyIdempotent

Use when you need a site_id, or the user asks about their websites, plan, limits, credits or page views. Lists every site with its URL and form message count, plus what the plan allows.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`text`	Yes	The answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).
`sites`	Yes	Every website of the account.
`account`	Yes	Plan, limits and usage of the signed-in account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / text

Added value: +{
+  "description": "The answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "account",
-  "sites"
-]New value: +[
+  "account",
+  "sites",
+  "text"
+]

Changed2 schema fields changedNov 2, 2026

removedOutput schema / properties / account / properties / email

Removed value: -{
-  "description": "The signed-in account's email.",
-  "type": "string"
-}

changedOutput schema / properties / account / required

Previous value: -[
-  "email",
-  "plan",
-  "websites",
-  "custom_domains",
-  "files_per_website",
-  "photos",
-  "credits",
-  "page_views_this_month",
-  "assistant_limits",
-  "upgrade_url",
-  "admin_users_per_website",
-  "part_limits_per_website"
-]New value: +[
+  "plan",
+  "websites",
+  "custom_domains",
+  "files_per_website",
+  "photos",
+  "credits",
+  "page_views_this_month",
+  "assistant_limits",
+  "upgrade_url",
+  "admin_users_per_website",
+  "part_limits_per_website"
+]

Changed3 schema fields changedOct 24, 2026

changedOutput schema / properties / account / properties / credits / description

Previous value: -"Credits for Ginta's own in-app AI."New value: +"Credits for Ginta's own in-app AI: balance without today's daily credits, and the daily credits left (used first)."

addedOutput schema / properties / account / properties / credits / properties / daily
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / properties / account / properties / credits / required

Previous value: -[
-  "balance",
-  "note"
-]New value: +[
+  "balance",
+  "daily",
+  "note"
+]

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / account / properties / part_limits_per_website

Added value: +{
+  "additionalProperties": {},
+  "description": "Caps of the shop, bookings and events per website (null = no limit).",
+  "properties": {
+    "bookings_per_month": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "shop_products": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "upcoming_events": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "shop_products",
+    "bookings_per_month",
+    "upcoming_events"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / account / required

Previous value: -[
-  "email",
-  "plan",
-  "websites",
-  "custom_domains",
-  "files_per_website",
-  "photos",
-  "credits",
-  "page_views_this_month",
-  "assistant_limits",
-  "upgrade_url",
-  "admin_users_per_website"
-]New value: +[
+  "email",
+  "plan",
+  "websites",
+  "custom_domains",
+  "files_per_website",
+  "photos",
+  "credits",
+  "page_views_this_month",
+  "assistant_limits",
+  "upgrade_url",
+  "admin_users_per_website",
+  "part_limits_per_website"
+]

Changed2 schema fields changedOct 18, 2026

addedOutput schema / properties / account / properties / photos

Added value: +{
+  "additionalProperties": {},
+  "description": "The owner's photos (attach_image) in use on all websites, and the plan's limit.",
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "used": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "used",
+    "limit"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / account / required

Previous value: -[
-  "email",
-  "plan",
-  "websites",
-  "custom_domains",
-  "files_per_website",
-  "credits",
-  "page_views_this_month",
-  "assistant_limits",
-  "upgrade_url",
-  "admin_users_per_website"
-]New value: +[
+  "email",
+  "plan",
+  "websites",
+  "custom_domains",
+  "files_per_website",
+  "photos",
+  "credits",
+  "page_views_this_month",
+  "assistant_limits",
+  "upgrade_url",
+  "admin_users_per_website"
+]

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's extra content is a summary of returned data, which the output schema also covers, so it adds only marginal behavioral context such as the completeness guarantee that all sites are returned.

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

Conciseness5/5

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

Two sentences, with the usage trigger front-loaded before the payload description. There is no filler, no restatement of the title, and every clause carries information an agent can act on.

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

Completeness5/5

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

A zero-parameter, read-only listing tool with full annotation coverage and an output schema needs only a clear when-to-use and a note on contents. Both are present, so nothing required for correct invocation is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The mention that it is used when a site_id is needed hints at how the result feeds other tools, which is a small useful addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists every site') and enumerates the payload ('URL and form message count, plus what the plan allows'). The 'every site' scope implicitly but clearly distinguishes it from the single-site sibling get_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives an explicit trigger ('Use when you need a site_id, or the user asks about their websites, plan, limits, credits or page views'), which is strong and covers the main call sites. It stops short of naming a when-not condition or pointing to alternatives such as get_site when only one site's detail is needed.

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

All Ginta 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?