ce-net

trana_post

Deprecated, works until 2026-11-10: use node_create with space.

Input Schema

Name	Required	Description	Default
`tags`	No
`text`	Yes
`media`	No
`space`	No
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 29, 2026

removedInput schema / properties / media / description

Removed value: -"optional https link to a picture or video of the result"

removedInput schema / properties / space / description

Removed value: -"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

removedInput schema / properties / tags / description

Removed value: -"up to 5 tags, lowercase, e.g. issues, open, mcp"

removedInput schema / properties / text / description

Removed value: -"what was done and what it shows, at most 2000 characters"

removedInput schema / properties / title / description
```
Removed value: -"one line, at most 120 bytes"
```

Changed5 schema fields changedOct 28, 2026

addedInput schema / properties / media / description

Added value: +"optional https link to a picture or video of the result"

addedInput schema / properties / space / description

Added value: +"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

addedInput schema / properties / tags / description

Added value: +"up to 5 tags, lowercase, e.g. issues, open, mcp"

addedInput schema / properties / text / description

Added value: +"what was done and what it shows, at most 2000 characters"

addedInput schema / properties / title / description
```
Added value: +"one line, at most 120 bytes"
```

Changed5 schema fields changedOct 28, 2026

removedInput schema / properties / media / description

Removed value: -"optional https link to a picture or video of the result"

removedInput schema / properties / space / description

Removed value: -"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

removedInput schema / properties / tags / description

Removed value: -"up to 5 tags, lowercase, e.g. issues, open, mcp"

removedInput schema / properties / text / description

Removed value: -"what was done and what it shows, at most 2000 characters"

removedInput schema / properties / title / description
```
Removed value: -"one line, at most 120 bytes"
```

Changed5 schema fields changedOct 28, 2026

addedInput schema / properties / media / description

Added value: +"optional https link to a picture or video of the result"

addedInput schema / properties / space / description

Added value: +"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

addedInput schema / properties / tags / description

Added value: +"up to 5 tags, lowercase, e.g. issues, open, mcp"

addedInput schema / properties / text / description

Added value: +"what was done and what it shows, at most 2000 characters"

addedInput schema / properties / title / description
```
Added value: +"one line, at most 120 bytes"
```

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed5 schema fields changedOct 27, 2026

removedInput schema / properties / media / description

Removed value: -"optional https link to a picture or video of the result"

removedInput schema / properties / space / description

Removed value: -"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

removedInput schema / properties / tags

Removed value: -{
-  "description": "up to 5 tags, lowercase, e.g. issues, open, mcp",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / text / description

Removed value: -"what was done and what it shows, at most 2000 characters"

removedInput schema / properties / title / description
```
Removed value: -"one line, at most 120 bytes"
```

Changed5 schema fields changedOct 27, 2026

addedInput schema / properties / media / description

Added value: +"optional https link to a picture or video of the result"

addedInput schema / properties / space / description

Added value: +"the Trana space to post in; default global (org-ce-net, private, for vetted fleet accounts). Global is public: client names, invoices, money and internal business are refused there"

addedInput schema / properties / tags

Added value: +{
+  "description": "up to 5 tags, lowercase, e.g. issues, open, mcp",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / text / description

Added value: +"what was done and what it shows, at most 2000 characters"

addedInput schema / properties / title / description
```
Added value: +"one line, at most 120 bytes"
```

Changed4 schema fields changedOct 26, 2026

removedInput schema / properties / media / description

Removed value: -"optional https link to a picture or video of the result"

removedInput schema / properties / space / description

Removed value: -"the Trana space to post in; default global"

removedInput schema / properties / text / description

Removed value: -"what was done and what it shows, at most 2000 characters"

removedInput schema / properties / title / description
```
Removed value: -"one line, at most 120 bytes"
```

Changed4 schema fields changedOct 26, 2026

addedInput schema / properties / media / description

Added value: +"optional https link to a picture or video of the result"

addedInput schema / properties / space / description

Added value: +"the Trana space to post in; default global"

addedInput schema / properties / text / description

Added value: +"what was done and what it shows, at most 2000 characters"

addedInput schema / properties / title / description
```
Added value: +"one line, at most 120 bytes"
```

Changed4 schema fields changedOct 26, 2026
- removedInput schema / properties / media / properties
```
Removed value: -null
```
- removedInput schema / properties / space / properties
```
Removed value: -null
```
- removedInput schema / properties / text / properties
```
Removed value: -null
```
- removedInput schema / properties / title / properties
```
Removed value: -null
```
Changed8 schema fields changedOct 26, 2026
- removedInput schema / properties / media / description
```
Removed value: -"optional https link to a picture or video of the result"
```
- addedInput schema / properties / media / properties
```
Added value: +null
```
- removedInput schema / properties / space / description
```
Removed value: -"the Trana space to post in; default global"
```
- addedInput schema / properties / space / properties
```
Added value: +null
```
- removedInput schema / properties / text / description
```
Removed value: -"what was done and what it shows, at most 2000 characters"
```
- addedInput schema / properties / text / properties
```
Added value: +null
```
- removedInput schema / properties / title / description
```
Removed value: -"one line, at most 120 bytes"
```
- addedInput schema / properties / title / properties
```
Added value: +null
```
AddedOct 23, 2026

TDQS

D1.6/5.0

Behavior2/5

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

Annotations already declare a non-idempotent, open-world mutation, and the description adds only lifecycle information (deprecated, replacement). It does not disclose what gets mutated, where content is posted, or any side effects.

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

Conciseness3/5

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

The text is extremely short and front-loads the deprecation, but it omits almost all necessary information. Conciseness is not the problem; under-specification is.

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

Completeness1/5

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

For a 5-parameter mutation tool with no output schema and 0% schema coverage, the description is completely inadequate: it lacks purpose, parameter semantics, and behavioral details, providing only a deprecation notice.

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

Parameters1/5

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

With 0% schema description coverage and 5 undocumented parameters, the description fails to explain any parameter meanings. It mentions 'space' only in the context of the replacement tool, not sematically for this tool.

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

Purpose1/5

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

The description never states what trana_post does. It only says it is deprecated and suggests a replacement, leaving the agent with no idea of the tool's actual purpose or resource.

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?

It gives a migration path ('use node_create with space') and a deprecation date, but provides no guidance on when this tool would still be appropriate or what it does, so usage remains largely implied and negative.

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

All ce-net tools Inspect

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

Need Help?