MCP IT Glue Server

update_document_jwt

Update document content in IT Glue using session auth when the public API cannot persist changes. Requires a valid cached session; otherwise prompts to run the session capture script.

Instructions

Update an existing document's content using session authentication.

This tool uses session authentication (cookies + XSRF token from browser) to update document content. This is REQUIRED because IT Glue's public API doesn't persist document content.

If no valid session is cached, this will return an error asking you to run the session capture script.

Args: organization_id: Organization ID (required - needed for internal API) document_id: The document ID (required) name: Document name (required - needed for update) content: New document content as HTML (required) public: Whether the document is publicly visible (default False)

Returns: JSON string with the updated document

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`public`	No
`content`	Yes
`document_id`	Yes
`organization_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden well. It discloses the authentication mechanism (cookies + XSRF token), the fact that session auth is required, and the failure behavior when no session exists. It does not discuss reversibility, side effects beyond the update, or permission requirements, but the core behavior is transparent.

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 well-structured: a one-line summary, a short rationale for the auth requirement, an error-condition note, a clear Args block, and a Returns line. Every sentence adds useful information; there is no filler or repetition of the schema.

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?

Given the moderate complexity of 5 parameters and an output schema, the description is complete. It covers why the tool exists, how authentication works, what to do on session failure, all parameter meanings, and the return type. An agent has enough context to invoke it correctly and interpret failure.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does. Every parameter is explained beyond its name: organization_id is 'needed for internal API', content is specified as HTML, public has its default, and name is marked as required for the update. This is exactly the kind of semantic addition agents need.

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 an existing document's content using session authentication.' It clearly identifies the tool's action and distinguishes it from the sibling update_document by emphasizing the required session-auth mechanism.

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?

The description explicitly states this tool is REQUIRED because the public API doesn't persist document content, giving clear rationale for choosing this variant. It also explains the error condition when no session is cached and directs the user to run the session capture script. However, it does not explicitly name an alternative or state when not to use this tool.

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

Deploy Server