Skip to main content
Glama
Sign In

Pageform

by io.pageform.mcp
OverviewDiscussionsAdmin

Server Details

Pageform is an AI-native data room platform with a remote MCP server for Claude and other MCP-compatible clients. Upload and organize documents, generate structured data rooms with AI, audit missing materials, create secure share links, and analyze investor engagement directly from your AI assistant. Built for fundraising, investor relations, diligence, and deal workflows. Connect securely through Pageform OAuth.

Website: https://pageform.io Documentation: https://pageform.io/docs/integrations/claude

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
15.4% over 21 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
Pageform

TDQS

C2.9/5.0

Scored across 61 tools

Disambiguation2/5

Four room-creation paths (generate_room, create_empty_room, create_matter_room, mirror_folder_room), roughly ten upload paths (prepare_upload/finish_upload, prepare_uploads/finish_uploads, upload_documents, upload_inline_documents, prepare_file_version(s)/finish_file_version(s), upload_file_version), and overlapping placement verbs (place_document vs ingest_documents vs move_document, delete vs unlink_*) all compete for the same intent. Descriptions do distinguish them (single vs batch, PUT vs attachment vs base64, room score vs structure critic), but an agent must read carefully and audit_room vs rate_room plus the overloaded generic delete remain genuinely confusable.

Naming Consistency3/5

Most names follow snake_case verb_noun, but the verb inventory is inconsistent: add_block/add_section versus place_document/place_folder versus ingest_documents versus upload_documents for closely related actions, plus singular/plural twins (prepare_upload/prepare_uploads). A bare 'delete' sits alongside properly qualified delete_section, delete_block, and revoke_share_link, and mirror_folder_room reverses the pattern.

Tool Count2/5

61 tools is heavy for this domain, and much of the volume comes from near-duplicate single-versus-batch pairs (prepare_file_version/prepare_file_versions, finish_upload/finish_uploads) and redundant upload entry points that could be collapsed into fewer parameterized tools. The surface is well over-scoped relative to the core workflows.

Completeness4/5

Coverage is broad: room lifecycle, sections, blocks, document placement and unlinking, folder mirroring, document versions, share links with access control, analytics at org/room/link scope, plus audit and critique. Minor gaps exist (no workspace update/delete, no explicit get_share_link metadata beyond access/analytics), but agents have workarounds.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedadd_block2 fields changed
      • changedInput schema / properties / config / description
        Previous value: -"Block config (server-normalized). heading: { text }. rich_text: { html }. ai_suggestion: { text }. table: { columns: [{ id, name }], rows: [{ id, cells: { [columnId]: string } }] }. link_embed: { links: [{ id, url, title? }], viewMode }. org_overview: { description }. divider: {}."New value: +"Block config (server-normalized). heading: { text }. rich_text: { html }. ai_suggestion: { text }. table: { columns: [{ id, name }], rows: [{ id, cells: { [columnId]: string } }] }. link_embed: { links: [{ id, url, title? }], viewMode }. divider: {}."
      • changedInput schema / properties / type / enum
        Previous value: -[
-  "heading",
-  "rich_text",
-  "text",
-  "table",
-  "ai_suggestion",
-  "featured_documents",
-  "folder_documents",
-  "divider",
-  "link_embed",
-  "image",
-  "video",
-  "org_overview"
-]New value: +[
+  "heading",
+  "rich_text",
+  "image",
+  "video",
+  "link_embed",
+  "table",
+  "divider",
+  "featured_documents",
+  "folder_documents",
+  "ai_suggestion"
+]
    • Changedupdate_block1 field changed
      • changedInput schema / properties / config / description
        Previous value: -"Block config. heading: { text }. rich_text: { html }. ai_suggestion: { text }. table: { columns, rows }. link_embed: { links, viewMode }. featured_documents: { document_ids, view_mode }. document_ids replaces that section's documents. folder_documents: { folder_ids, view_mode }. folder_ids replaces that section's folders. image: { document_id, size, alignment }. document_id sets the image. video: { videos, viewMode }. videos replaces the videos. org_overview: { description }. divider: {}."New value: +"Block config. heading: { text }. rich_text: { html }. ai_suggestion: { text }. table: { columns, rows }. link_embed: { links, viewMode }. featured_documents: { document_ids, view_mode }. document_ids replaces that section's documents. folder_documents: { folder_ids, view_mode }. folder_ids replaces that section's folders. image: { document_id, size, alignment }. document_id sets the image. video: { videos, viewMode }. videos replaces the videos. divider: {}."
  2. 2 tool updates
    • Addedget_share_link_access
    • Addedupdate_share_link_access
  3. 59 tool updates
    • Changedadd_block2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "section_id",
-  "type"
-]New value: +[
+  "section_id",
+  "type",
+  "context"
+]
    • Changedadd_section2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "title"
-]New value: +[
+  "title",
+  "context"
+]
    • Changedaudit_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedclassify_upload_structure2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "dataroom_type"
-]New value: +[
+  "dataroom_type",
+  "context"
+]
    • Changedcreate_empty_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "context"
+]
    • Changedcreate_matter_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "room_name",
-  "room_description"
-]New value: +[
+  "room_name",
+  "room_description",
+  "context"
+]
    • Changedcreate_share_link2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "scope"
-]New value: +[
+  "scope",
+  "context"
+]
    • Changedcreate_workspace2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "name",
-  "workspace_type"
-]New value: +[
+  "name",
+  "workspace_type",
+  "context"
+]
    • Changeddelete2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "scope"
-]New value: +[
+  "scope",
+  "context"
+]
    • Changeddelete_block2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changeddelete_section2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "section_id"
-]New value: +[
+  "section_id",
+  "context"
+]
    • Changedfinish_file_version2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "s3_key",
-  "file_name",
-  "byte_size"
-]New value: +[
+  "document_id",
+  "s3_key",
+  "file_name",
+  "byte_size",
+  "context"
+]
    • Changedfinish_file_versions2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
    • Changedfinish_upload2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "s3_key",
-  "file_name",
-  "byte_size"
-]New value: +[
+  "document_id",
+  "s3_key",
+  "file_name",
+  "byte_size",
+  "context"
+]
    • Changedfinish_uploads2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
    • Changedgenerate_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "dataroom_type"
-]New value: +[
+  "dataroom_type",
+  "context"
+]
    • Changedget_document2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id"
-]New value: +[
+  "document_id",
+  "context"
+]
    • Changedget_document_catalog2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedget_generation_status2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "job_id"
-]New value: +[
+  "job_id",
+  "context"
+]
    • Changedget_org_analytics2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedget_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "data_room_id"
-]New value: +[
+  "data_room_id",
+  "context"
+]
    • Changedget_room_analytics2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedget_room_structure2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedget_share_link_analytics2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "share_link_id"
-]New value: +[
+  "share_link_id",
+  "context"
+]
    • Changedget_upload_link2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedget_workspace2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedingest_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_folders2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_generation_jobs2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_room_types2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_rooms2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_share_links2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedlist_unplaced_library_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedmirror_folder_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "dataroom_type",
-  "room_name",
-  "room_description"
-]New value: +[
+  "dataroom_type",
+  "room_name",
+  "room_description",
+  "context"
+]
    • Changedmove_document2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "to_section_id"
-]New value: +[
+  "document_id",
+  "to_section_id",
+  "context"
+]
    • Changedmove_folder2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "to_section_id"
-]New value: +[
+  "to_section_id",
+  "context"
+]
    • Changedplace_document2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "section_id"
-]New value: +[
+  "document_id",
+  "section_id",
+  "context"
+]
    • Changedplace_folder2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "section_id"
-]New value: +[
+  "section_id",
+  "context"
+]
    • Changedplace_image2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "section_id"
-]New value: +[
+  "document_id",
+  "section_id",
+  "context"
+]
    • Changedplace_video2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "section_id"
-]New value: +[
+  "section_id",
+  "context"
+]
    • Changedprepare_file_version2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "file_name",
-  "byte_size"
-]New value: +[
+  "document_id",
+  "file_name",
+  "byte_size",
+  "context"
+]
    • Changedprepare_file_versions2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
    • Changedprepare_upload2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "file_name",
-  "byte_size"
-]New value: +[
+  "file_name",
+  "byte_size",
+  "context"
+]
    • Changedprepare_uploads2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
    • Changedrate_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedrename_document2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "title"
-]New value: +[
+  "document_id",
+  "title",
+  "context"
+]
    • Changedrevoke_share_link2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "share_link_id"
-]New value: +[
+  "share_link_id",
+  "context"
+]
    • Changedsearch_library_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "context"
+]
    • Changedunlink_document2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedunlink_folder2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedunlink_image2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedunlink_video2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedupdate_block3 fields changed
      • addedInput schema / properties / config / description
        Added value: +"Block config. heading: { text }. rich_text: { html }. ai_suggestion: { text }. table: { columns, rows }. link_embed: { links, viewMode }. featured_documents: { document_ids, view_mode }. document_ids replaces that section's documents. folder_documents: { folder_ids, view_mode }. folder_ids replaces that section's folders. image: { document_id, size, alignment }. document_id sets the image. video: { videos, viewMode }. videos replaces the videos. org_overview: { description }. divider: {}."
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "block_id"
-]New value: +[
+  "block_id",
+  "context"
+]
    • Changedupdate_room2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • addedInput schema / required
        Added value: +[
+  "context"
+]
    • Changedupdate_section2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "section_id"
-]New value: +[
+  "section_id",
+  "context"
+]
    • Changedupload_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
    • Changedupload_file_version2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "document_id",
-  "file"
-]New value: +[
+  "document_id",
+  "file",
+  "context"
+]
    • Changedupload_inline_documents2 fields changed
      • addedInput schema / properties / context
        Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
      • changedInput schema / required
        Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "context"
+]
  4. 59 tool updates
    • First observedadd_block
    • First observedadd_section
    • First observedaudit_room
    • First observedclassify_upload_structure
    • First observedcreate_empty_room
    • First observedcreate_matter_room
    • First observedcreate_share_link
    • First observedcreate_workspace
    • First observeddelete
    • First observeddelete_block
    • First observeddelete_section
    • First observedfinish_file_version
    • First observedfinish_file_versions
    • First observedfinish_upload
    • First observedfinish_uploads
    • First observedgenerate_room
    • First observedget_document
    • First observedget_document_catalog
    • First observedget_generation_status
    • First observedget_org_analytics
    • First observedget_room
    • First observedget_room_analytics
    • First observedget_room_structure
    • First observedget_share_link_analytics
    • First observedget_upload_link
    • First observedget_workspace
    • First observedingest_documents
    • First observedlist_documents
    • First observedlist_folders
    • First observedlist_generation_jobs
    • First observedlist_room_types
    • First observedlist_rooms
    • First observedlist_share_links
    • First observedlist_unplaced_library_documents
    • First observedmirror_folder_room
    • First observedmove_document
    • First observedmove_folder
    • First observedplace_document
    • First observedplace_folder
    • First observedplace_image
    • First observedplace_video
    • First observedprepare_file_version
    • First observedprepare_file_versions
    • First observedprepare_upload
    • First observedprepare_uploads
    • First observedrate_room
    • First observedrename_document
    • First observedrevoke_share_link
    • First observedsearch_library_documents
    • First observedunlink_document
    • First observedunlink_folder
    • First observedunlink_image
    • First observedunlink_video
    • First observedupdate_block
    • First observedupdate_room
    • First observedupdate_section
    • First observedupload_documents
    • First observedupload_file_version
    • First observedupload_inline_documents

Publisher details

Operator
Pageform
Operator website
https://pageform.io
Vendor relationship
First-party
Documentation
https://pageform.io/docs/integrations/claude
Trust center
Not applicable
Restrictions
Not applicable

Related MCP Connectors

Related MCP Servers

  • MCP for Nextcloud

    sintax-tech
    A
    license
    Not graded
    quality
    A
    maintenance
    A native Nextcloud app that exposes the instance as an MCP server so Claude and other MCP clients can read, search, and (with admin-granted permissions) edit files, notes, calendars, Deck cards, and Talk conversations. It runs inside Nextcloud with OAuth or app-password sign-in, applying each user's own Nextcloud permissions and admin-controlled per-operation grants.
    14
    AGPL 3.0

  • clio-mcp

    ToddHebebrand
    F
    license
    B
    quality
    D
    maintenance
    A standalone MCP server that enables Claude Desktop to manage Clio legal practice matters, documents, billing, and more via ~46 tools, with secure OAuth and audit logging.
    46
    -

  • Bee

    liyjie00
    A
    license
    Not graded
    quality
    B
    maintenance
    A remote MCP server that lets Claude and other MCP clients list, search, read, create, edit, rename, and move folders and documents, draw and describe whiteboards, and read, add, reply to, and resolve comments with the signed-in user's permissions.
    22 npm
    AGPL 3.0
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