Skip to main content
Glama
Sign In

WeInc

by io.github.umairalisadaqat
OverviewDiscussionsAdmin

Publish website

publish_website
DestructiveIdempotent

Put one of the person's own WeInc websites live on the internet at its weinc.app address (or its connected domain), exactly like pressing Publish in the editor. Usually takes 15-45 seconds and returns the live link; if it takes longer it answers 'publishing' and website_details gives the live link shortly after. The site becomes public, so ask the person before calling this. The account's plan sets how many sites can be live at once; a refusal explains why.

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": {
      "projectId": "<projectId>"
    },
    "name": "publish_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesWebsite id from my_websites or create_website_from_template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: expected duration (15-45s), the deferred 'publishing' response state and that website_details will surface the link later, the public visibility consequence, and that plan-based refusals are explained. These are exactly the operational facts an agent needs before firing a destructive, open-world write.

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?

Four sentences, each carrying distinct information: what it does, how long it takes and what it returns, the consent requirement, and plan limitations. Front-loaded and free of filler.

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?

No output schema exists, yet the description covers the return shape (live link or 'publishing' placeholder), timing, failure mode, and the consent/safety requirement. Nothing material is missing for a one-parameter publish action.

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?

Only one parameter and the schema already documents it at 100% coverage with its source tools (my_websites, create_website_from_template). The description adds only the ownership constraint ('one of the person's own'), which is marginal but real.

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 (publish/make live), the resource (one of the person's own WeInc websites), and the target (weinc.app address or connected domain). The analogy 'exactly like pressing Publish in the editor' pins the semantics down and separates it from create_website_from_template, start_website, and get_preview_urls.

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?

Explicit prerequisites and conditions: the site is the person's own, it becomes public so consent should be sought first, and plan limits gate how many sites can be live. It does not explicitly contrast with sibling tools such as start_website or get_preview_urls, which keeps it from a 5.

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

All WeInc toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources