Skip to main content
Glama

Vee3

by io.github.Vee3io

pages.edit

Update a hosted static website for this Vee3 account.

Change the display name and/or the public slug. Changing the slug moves the preview hostname to {slug}.vee3.site and issues a new TLS certificate. An attached custom domain stays in place. Pass at least one of name or slug.

Cost = 20 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name for the page. Does not change the public URL. Pass an empty value to clear the name. At most 80 characters.
slugNoNew page slug used for the public hostname ({slug}.vee3.site). Must be unique across Vee3. Lowercase alphanumeric characters and hyphens only; 1-48 characters; must start and end with an alphanumeric character.
page_idYesPage id to update.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPublic HTTPS URL for the page. Uses the custom domain when one is attached.
nameNoDisplay name for the page, if set.
slugNoPage slug.
statusNoCurrent page status.
page_idNoUnique identifier for the page.
hostnameNoPreview hostname ({slug}.vee3.site). Always present, including when a custom domain is attached.
created_atNoWhen the page was created.
updated_atNoWhen the page record was last updated.
custom_domainNoCustom hostname attached to the page, if any.
last_deployed_atNoWhen files were last deployed to the page.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carres the full burden. It discloses important side effects: changing the slug moves the preview hostname, issues a new TLS certificate, and leaves an attached custom domain in place. It also discloses the 20-token cost and the at-last-one-parameter requirement.

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?

The description is compact and well-structured: purpose is front-loaded, then side effects and usage constraints follow. Each sentence carries distinct information, and the cost line is concise and relevant.

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?

For a 3-parameter mutation tool with no annotations, the description covers purpose, required/optional inputs, the at-least-one constraint, behavioral side effects, cost, and account scope. An output schema exists, so return-value explanation is unnecessary. Nothing needed to call the tool correctly 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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by stating the cross-parameter constraint 'Pass at least one of name or slug' and by explaining the consequences of changing slug. This is genuine value beyond the per-field schema descriptions.

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?

The description opens with a specific verb and resource ('Update a hosted static website for this Vee3 account') and immediately narrows the scope to changing the display name and/or slug. This clearly distinguishes it from sibling pages tools such as create, delete, deploy, get, and list.

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?

It clearly states when to use the tool: to change the display name and/or public slug, and it adds the key constraint 'Pass at least one of name or slug.' However, it does not explicitly name alternative tools such as pages.deploy or pages.set_custom_domain, so it stops short of full exclusion guidance.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources