ATTIM

Publish site

publish_site

Publish files as a new site at .attim.link. Signed in, the site is permanent in the account; without an account it is temporary (ttlSeconds sets how long). To keep a temporary site, ask for the user's email and call claim_site.

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": {
      "files": "<files>"
    },
    "name": "publish_site"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No
`files`	Yes
`ttlSeconds`	No
`workspaceId`	No
`passwordProtection`	No

Output Schema

Name	Required	Description	Default
`slug`	Yes
`status`	No
`siteUrl`	Yes
`anonymous`	No
`expiresAt`	No
`versionId`	No
`claimToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 12, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / files / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / files / items / properties / contentType / minLength
```
Removed value: -1
```
- removedInput schema / properties / files / items / properties / path / minLength
```
Removed value: -1
```
- removedInput schema / properties / finalize
```
Removed value: -{
-  "default": true,
-  "type": "boolean"
-}
```
- removedInput schema / properties / passwordProtection / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / passwordProtection / properties / password / minLength
```
Removed value: -1
```
- removedInput schema / properties / workspaceId / minimum
```
Removed value: -1
```
- removedOutput schema / properties / acceptedBytes
```
Removed value: -{
-  "type": "integer"
-}
```
- removedOutput schema / properties / passwordProtected
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedOutput schema / properties / previousVersionId
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / restoredFromVersionId
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / title
```
Removed value: -{
-  "type": "string"
-}
```
First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only say it is a non-read-only, non-idempotent, open-world write. The description adds genuinely new behavioral facts: site lifetime depends on authentication state, temporary sites expire per ttlSeconds, and unclaimed temporary sites are presumably lost. It does not say what happens on a slug collision or how password protection affects the outcome.

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?

Three short sentences, front-loaded with the action and URL outcome, then the auth/ttl consequence, then the remediation path. No filler or repetition of the tool name.

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?

An output schema exists, so return values need no explanation, and the auth/expiry model is well covered. However, for a non-idempotent open-world write with five undocumented parameters, the definition omits collision/overwrite behavior, how files content vs contentBase64 is chosen, and the role of workspaceId and passwordProtection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters including nested objects, so the description has to carry the burden. It only clarifies slug (subdomain) and ttlSeconds (temporary lifetime); files, workspaceId, and the passwordProtection sub-object are left entirely to the bare schema types.

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 gives a specific verb and resource ("Publish files as a new site") plus the exact resulting URL shape (<slug>.attim.link). The phrase "as a new site" distinguishes it from sibling mutation tools like edit_site, update_site, and copy_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?

It explicitly routes an agent to the alternative claim_site and states the trigger condition (user wants a temporary site to persist, so collect their email first). It does not cover when an agent should choose this over edit_site or copy_site, but the main branching decision is spelled out.

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

All ATTIM tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?