SignNow MCP Server

Official

by signnow

Overview Schema Related Servers Score Discussions

Python

Hybrid

Update document text fields

update_document_fields

DestructiveIdempotent

Update text fields in multiple documents by providing document IDs and field name-value pairs.

Instructions

Update text fields in multiple documents (only individual documents, not document groups)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`update_requests`	Yes	Array of document field update requests

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes	Array of update results for each document

Schema Changelog

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

Addedv2.4.0May 27, 2026
Removedv2.2.3May 20, 2026

Changed13 schema fields changedv2.2.1May 12, 2026

removedInput schema / $defs

Removed value: -{
-  "FieldToUpdate": {
-    "description": "Single field to update in a document.",
-    "properties": {
-      "name": {
-        "description": "Name of the field to update",
-        "type": "string"
-      },
-      "value": {
-        "description": "New value for the field",
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "value"
-    ],
-    "type": "object"
-  },
-  "UpdateDocumentFields": {
-    "description": "Request model for updating document fields.",
-    "properties": {
-      "document_id": {
-        "description": "ID of the document to update",
-        "type": "string"
-      },
-      "fields": {
-        "description": "Array of fields to update with their new values",
-        "items": {
-          "$ref": "#/$defs/FieldToUpdate"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "document_id",
-      "fields"
-    ],
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / update_requests / items / $ref
```
Removed value: -"#/$defs/UpdateDocumentFields"
```
addedInput schema / properties / update_requests / items / description
```
Added value: +"Request model for updating document fields."
```

addedInput schema / properties / update_requests / items / properties

Added value: +{
+  "document_id": {
+    "description": "ID of the document to update",
+    "type": "string"
+  },
+  "fields": {
+    "description": "Array of fields to update with their new values",
+    "items": {
+      "description": "Single field to update in a document.",
+      "properties": {
+        "name": {
+          "description": "Name of the field to update",
+          "type": "string"
+        },
+        "value": {
+          "description": "New value for the field",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "value"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / update_requests / items / required
```
Added value: +[
+  "document_id",
+  "fields"
+]
```
addedInput schema / properties / update_requests / items / type
```
Added value: +"object"
```

removedOutput schema / $defs

Removed value: -{
-  "UpdateDocumentFieldsResult": {
-    "description": "Result of updating document fields.",
-    "properties": {
-      "document_id": {
-        "description": "ID of the document that was updated",
-        "type": "string"
-      },
-      "reason": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Reason for failure if updated is false"
-      },
-      "updated": {
-        "description": "Whether the document fields were successfully updated",
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "document_id",
-      "updated"
-    ],
-    "type": "object"
-  }
-}

removedOutput schema / properties / results / items / $ref
```
Removed value: -"#/$defs/UpdateDocumentFieldsResult"
```
addedOutput schema / properties / results / items / description
```
Added value: +"Result of updating document fields."
```

addedOutput schema / properties / results / items / properties

Added value: +{
+  "document_id": {
+    "description": "ID of the document that was updated",
+    "type": "string"
+  },
+  "reason": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Reason for failure if updated is false"
+  },
+  "updated": {
+    "description": "Whether the document fields were successfully updated",
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / results / items / required
```
Added value: +[
+  "document_id",
+  "updated"
+]
```
addedOutput schema / properties / results / items / type
```
Added value: +"object"
```

Changed9 schema fields changedv1.0.0Jan 3, 2026

addedInput schema / $defs

Added value: +{
+  "FieldToUpdate": {
+    "description": "Single field to update in a document.",
+    "properties": {
+      "name": {
+        "description": "Name of the field to update",
+        "type": "string"
+      },
+      "value": {
+        "description": "New value for the field",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "value"
+    ],
+    "type": "object"
+  },
+  "UpdateDocumentFields": {
+    "description": "Request model for updating document fields.",
+    "properties": {
+      "document_id": {
+        "description": "ID of the document to update",
+        "type": "string"
+      },
+      "fields": {
+        "description": "Array of fields to update with their new values",
+        "items": {
+          "$ref": "#/$defs/FieldToUpdate"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "document_id",
+      "fields"
+    ],
+    "type": "object"
+  }
+}

addedInput schema / properties / update_requests / examples

Added value: +[
+  [
+    {
+      "document_id": "abc123",
+      "fields": [
+        {
+          "name": "FieldName1",
+          "value": "New Value 1"
+        },
+        {
+          "name": "FieldName2",
+          "value": "New Value 2"
+        }
+      ]
+    },
+    {
+      "document_id": "def456",
+      "fields": [
+        {
+          "name": "FieldName3",
+          "value": "New Value 3"
+        }
+      ]
+    }
+  ]
+]

removedInput schema / properties / update_requests / title
```
Removed value: -"Update Requests"
```
removedOutput schema / $defs / UpdateDocumentFieldsResult / properties / document_id / title
```
Removed value: -"Document Id"
```
removedOutput schema / $defs / UpdateDocumentFieldsResult / properties / reason / title
```
Removed value: -"Reason"
```
removedOutput schema / $defs / UpdateDocumentFieldsResult / properties / updated / title
```
Removed value: -"Updated"
```
removedOutput schema / $defs / UpdateDocumentFieldsResult / title
```
Removed value: -"UpdateDocumentFieldsResult"
```
removedOutput schema / properties / results / title
```
Removed value: -"Results"
```

removedOutput schema / title

Removed value: -"UpdateDocumentFieldsResponse"

First observedOct 6, 2025

TDQS

A4.2/5.0

Behavior4/5

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

The description confirms mutation (consistent with annotations) and adds a specific constraint not covered by annotations. Annotations already provide safety profile, so the description adds value without contradiction.

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?

A single sentence that is front-loaded with the core action and constraints. No wasted words.

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

Completeness4/5

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

Given the presence of an output schema and full annotation coverage, the description adequately covers the tool's purpose and constraints. It is complete for the complexity level.

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?

With 100% schema description coverage, the schema already explains the update_requests structure in detail. The description adds no additional parameter-level semantics beyond stating the action and scope, so baseline 3 is appropriate.

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 clearly states the verb 'update', the resource 'text fields', and the scope 'multiple documents' with explicit exclusion of 'document groups', fully distinguishing from sibling tools.

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 provides clear direction by stating that only individual documents are supported, not groups, guiding the agent on when to use this tool. No explicit alternatives are named, but the exclusion is helpful.

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

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/signnow/sn-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server