Unified.to MCP Server
Server Details
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
- Status
- Healthy
- Uptime
- 55.6% over 38 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 25 tools
Each tool is scoped to a distinct resource and action, with clear get/list/create/update/remove boundaries. Even the similar webhook tools are separated by their target (webhook vs webhook_trigger), and cross-references in descriptions remove ambiguity.
The vast majority follow a consistent verb_unified_noun pattern, making the set predictable. Minor deviations like search_docs, get_unified_connection_mcp_url, and update_unified_webhook_trigger prevent a perfect score.
At 25 tools, the server sits at the upper boundary of what feels heavy for an MCP tool set. The count is justified by the number of resource types, but the CRUD duplication across connections, webhooks, environments, and secrets managers makes it borderline.
Core workflows for connections and webhooks are complete, with create/get/list/update/remove coverage. Minor gaps exist, such as no get/update for environments and no update for secrets managers, but these can be worked around.
Available Tools
25 toolscreate_unified_connectionCreate connectionADestructiveInspect
Create a connection in the connected account. Returns the created connection record. Requires the connection fields in the request body. Creates a new record; to modify an existing connection, use update_unified_connection.
| Name | Required | Description | Default |
|---|---|---|---|
| auth | No | An authentication object that represents a specific authorized user's connection to an integration | |
| is_paused | No | Whether this integration has exceed the monthly limit of the plan | |
| categories | Yes | The Integration categories that this connection supports | |
| environment | No | ||
| permissions | Yes | Array | |
| workspace_id | No | (reference to KmsSpace) | |
| external_xref | No | customer's user ID | |
| last_healthy_at | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| integration_name | No | ||
| integration_type | Yes | The integration type | |
| last_unhealthy_at | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| secretsmanager_id | No | the ID of the SecretsManager object | |
| secretsmanager_key | No | the key/path/name of the secret within the vault | |
| last_unhealthy_code | No | The HTTP status code that caused the last unhealthy status |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's 'Creates a new record' aligns with these. The description adds that it returns the created record, which is useful, but does not disclose other side effects or requirements beyond what annotations convey. Given annotations cover the safety profile, this is adequate but not extensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main purpose and return value, then gives a clear directive about the alternative. Every word earns its place; no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having 14 parameters including a nested auth object and three required fields, the description provides no guidance on constructing the request beyond generic phrasing. It does not explain what integration_type should be, how to populate auth, or the significance of categories/permissions. With no output schema, the return structure is also undefined. This is insufficient for a complex create operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 86%, so the schema already documents most parameters. The description only generically says 'Requires the connection fields in the request body,' which adds little beyond the required fields in the schema. It does not explain the structure of the auth object or how to choose integration_type, but the schema provides some descriptions. This meets the baseline but does not go further.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Create a connection in the connected account.' It also mentions the return value ('Returns the created connection record') and explicitly differentiates from the update operation by naming `update_unified_connection` as the alternative for modifying existing connections. This distinguishes it from sibling create tools for environment, webhook, and secretsmanager.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'to modify an existing connection, use `update_unified_connection`', providing a clear when-not-to-use directive. However, it does not mention when to use get/list connections or any prerequisites like checking for duplicate connections. The guidance is focused on the modification alternative but lacks broader usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
create_unified_environmentCreate environmentADestructiveInspect
Create an environment in the connected account. Returns the created environment record. Requires the environment fields in the request body. Creates a new record; to search or list environments, use list_unified_environments.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotation Contradiction: the description says 'Creates a new record' and describes a non-destructive creation operation, while the annotations mark `destructiveHint: true`. The description gives no explanation of destructive side effects and instead implies the opposite behavior. This is a serious inconsistency for an agent relying on both signals.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three compact sentences cover purpose, return value, request-body requirement, and the relevant alternative. There is minor redundancy in saying both 'Create an environment' and 'Creates a new record,' but the text is otherwise efficient and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core action, return value, body requirement, and an alternative tool. However, with no output schema and an empty input schema, it should be more explicit about what 'environment fields' are required and what non-idempotent or destructive behavior might occur, especially given the conflicting destructiveHint annotation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero properties, so the baseline is high. The description adds useful guidance by stating that environment fields must be supplied in the request body, which is not visible in the empty schema. However, it remains vague about what those fields are, so it does not fully replace structured parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Create'), a specific resource ('environment'), and the scope ('in the connected account'). It also clarifies the outcome ('Returns the created environment record') and explicitly separates itself from listing by naming `list_unified_environments`.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent to use `list_unified_environments` for searching or listing environments, which is a clear when-not-to-use condition with a named alternative. It also notes that environment fields are required in the request body, signaling a prerequisite for invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
create_unified_webhookCreate webhookBDestructiveInspect
Create a webhook in the connected account. Returns the created webhook record. Requires the webhook fields in the request body. Creates a new record; to modify an existing webhook, use update_unified_webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| meta | No | ||
| runs | No | An array of the most revent virtual webhook runs | |
| event | Yes | ||
| db_url | No | ||
| fields | No | ||
| db_type | No | ||
| filters | No | ||
| is_beta | No | ||
| hook_url | No | The URL of the webhook | |
| interval | No | The interval (in minutes) to check for updated/new objets | |
| db_schema | No | ||
| is_paused | No | ||
| checked_at | No | The last date/time that a check was done on this object (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| is_healthy | No | ||
| environment | No | ||
| object_type | Yes | The object to return (eg | |
| webhook_type | No | ||
| workspace_id | No | (reference to KmsSpace) | |
| connection_id | Yes | ||
| db_name_prefix | No | ||
| page_max_limit | No | ||
| integration_type | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, so the description doesn't need to repeat that. It adds the fact that it 'Returns the created webhook record' and mentions the requirement for 'webhook fields in the request body,' which provides some behavioral context. However, it does not disclose details like idempotency (though annotations say idempotentHint=false) or potential side effects such as triggering events, rate limits, or confirmation requirements, which would be valuable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise—three sentences—and front-loads the core action and return value. It efficiently uses the third sentence to point to the sibling tool for updates. However, it could be more structured by explicitly listing required parameters or adding a brief 'When to use' section, but overall it is appropriately sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (22 parameters, 3 required, 27% schema coverage, no output schema, nested objects) and the absence of a rich schema, the description is inadequate. It fails to explain which 'webhook fields' are required, what the different webhook types (virtual vs native) mean, how 'event' interacts with 'object_type,' or what the return record contains beyond being a webhook. An agent would struggle to construct a valid request without opening the schema and even then, many parameters remain unclear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 27%, meaning most parameters are undocumented in the schema. The description provides almost no parameter guidance beyond saying 'webhook fields' are required, but it fails to specify which fields (beyond the schema's required list) or explain the meaning of key parameters like 'event,' 'object_type,' 'hook_url,' 'webhook_type,' or 'filters.' The description should compensate for the low schema coverage but does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Create a webhook'), the resource ('in the connected account'), and notes that it returns the created record. It also distinguishes itself from update_unified_webhook by saying 'Creates a new record; to modify an existing webhook, use update_unified_webhook.' This is clear, though it could be more specific about the required fields beyond 'webhook fields.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool (to create a new webhook) and provides an alternative (update_unified_webhook) for modification, which serves as a when-not. However, it does not mention other related tools like list_unified_webhooks for existing webhooks or the trigger update tool, which could be relevant context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
create_unified_workspace_secretsmanagerCreate secrets managerDDestructiveInspect
create secrets manager
| Name | Required | Description | Default |
|---|---|---|---|
| dcs | No | data-regions | |
| auth | Yes | secrets-manager specific authentication values | |
| name | Yes | ||
| type | Yes | ||
| workspace_id | No | (reference to KmsSpace) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral information beyond what annotations already declare. Annotations indicate readOnlyHint=false and destructiveHint=true, implying a write operation with potentially destructive side effects, but the description merely says 'create'. It does not disclose what gets created, what existing resources might be affected, or any authentication/role requirements. It adds zero value over the structured metadata.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but under-specified. It is not a model of conciseness; it omits essential context. There is no front-loaded information because there is no information at all. This is an under-specification, not a deliberate concise summary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a creation operation with no output schema, several parameters including nested objects and enums, and destructive annotations. The description 'create secrets manager' does nothing to help an agent understand what a secrets manager is, what required auth values look like, or what side effects occur. For such a complex tool, this is wholly inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description contains no information about any of the five parameters (dcs, auth, name, type, workspace_id). Even though the schema provides some descriptions for three fields, the description itself adds no meaning. It does not explain the enum values for type, the structure of auth, or the role of workspace_id. With 60% schema coverage, the description could compensate but does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. There is no mention of when to use this tool instead of alternatives like list_unified_workspace_secretsmanagers or get_unified_workspace_secretsmanager, nor any indication of prerequisites or conditions. The description gives no context to choose between tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_apicallGet API callARead-onlyIdempotentInspect
Retrieve a single apicall by its ID from the connected account. Returns the full apicall record. Requires id (obtained from list_unified_apicalls). Use when you already have the ID; to search or list apicalls, use list_unified_apicalls.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the apicall to get |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds context about the scope ('from the connected account') and the return ('full apicall record'), which is useful but does not go beyond what annotations imply. No contradictions with annotations, and the added details are minor.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. The primary action is front-loaded, followed by the requirement and a clear alternative. Every sentence contributes meaning, and the structure is optimal for quick scanning by an agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get-by-ID tool with one parameter, no output schema, and annotations covering safety, the description is complete. It covers what the tool does, when to use it, where the ID comes from, and what it returns. Nothing an agent needs to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already fully describes the `id` parameter (100% coverage). The description adds value by specifying that the ID is obtained from `list_unified_apicalls`, which is a source hint beyond the schema's generic description. This extra context helps the agent understand where the value comes from, so it earns a score above the baseline of 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Retrieve') and resource ('single apicall by its ID'), and explicitly distinguishes itself from the sibling `list_unified_apicalls` by noting it retrieves a single record rather than searching or listing. This makes it immediately clear what the tool does and how it differs from alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool ('Use when you already have the ID') and when not to ('to search or list apicalls, use `list_unified_apicalls`'), naming the alternative directly. It also tells the agent where to obtain the required `id` (from `list_unified_apicalls`), leaving no ambiguity about usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_connectionGet connectionARead-onlyIdempotentInspect
Retrieve a single connection by its ID from the connected account. Returns the full connection record. Requires id (obtained from list_unified_connections). Use when you already have the ID; to search or list connections, use list_unified_connections.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the connection to get |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds behavioral context by stating it 'Returns the full connection record' and that the ID is 'obtained from `list_unified_connections`', which provides useful provenance. It does not contradict annotations, and while it doesn't detail error handling or auth, the read-only nature is adequately covered by annotations plus the description's clarity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundant words. It leads with the primary action, then provides the return behavior and usage guidance. Every sentence earns its place, and the structure is front-loaded with the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only retrieval tool with no output schema and no nested objects, the description is complete. It explains what the tool does, when to use it, where to get the required ID, and what the return value is. Nothing essential is missing for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% since the only parameter `id` has a description. The description adds value beyond the schema by specifying that the ID comes from `list_unified_connections`, which helps the agent understand where to obtain valid input. This is meaningful supplementary information beyond the schema's bare definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Retrieve a single connection by its ID'), the resource ('connection'), and the scope ('from the connected account'). It also distinguishes itself from the sibling list tool by explicitly naming `list_unified_connections` as the alternative for searching or listing, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage guidance: 'Use when you already have the ID; to search or list connections, use `list_unified_connections`.' This directly tells the agent when to invoke this tool versus the alternative, leaving no ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_connection_mcp_urlGenerate a connection-scoped MCP URLAInspect
Get the MCP remote server URL for a specific connection ID. Returns a ready-to-use, connection-scoped Streamable HTTP MCP endpoint that exposes that connection's integration-specific tools. Authenticate with a workspace API key to use this. The URL embeds a credential and grants tool access without a further login, so treat it as a secret. It does NOT expire on its own. Revocation depends on the mode (see the mode parameter): an 'api'-mode URL carries the workspace API key and is revoked by rotating that key (which affects every URL that used it); a 'user'-mode URL is scoped to this one connection and is revoked by deleting the connection. Optional server options (permissions, tools, aliases, defer_tools, hide_sensitive, include_external_tools) are baked into the returned URL as query parameters.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Authentication mode for the generated URL | |
| tools | No | Comma-separated list of tool IDs or wildcard patterns to limit which tools the URL exposes (e | |
| aliases | No | Custom description aliases in the form 'key:alt1,alt2;key2:alt3' to improve tool matching (e | |
| defer_tools | No | Defer tool loading to reduce context usage | |
| permissions | No | Comma-separated permission scopes to limit the tools exposed by the URL (e | |
| connection_id | Yes | The ID of the connection to generate an MCP remote URL for | |
| hide_sensitive | No | When true, strips PII and other sensitive fields from tool responses before they reach the LLM | |
| include_external_tools | No | When true, exposes the vendor's raw passthrough endpoints as additional callable MCP tools |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes well beyond the sparse annotations by disclosing that the URL embeds a credential, does not expire on its own, and has mode-dependent revocation behavior. It even warns that rotating an api-mode key affects every URL that used it. This is rich behavioral context that an agent cannot get from the schema or annotations alone.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the tool's purpose and output, then logically moves through authentication, secret handling, revocation, and optional parameters. It is longer than a simple one-liner, but the length is justified by the security-sensitive nature of the operation, and every sentence carries relevant information without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the key concerns: what is returned, how to authenticate, security implications, non-expiry, revocation, and how optional parameters affect the output. However, it does not specify the default behavior or requirement of the optional mode parameter beyond the enum, and it only loosely characterizes the return format since there is no output schema. These are minor gaps for an otherwise rich description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the mode parameter: api-mode carries the workspace API key and is revoked by rotation, while user-mode is scoped to the connection and revoked by deletion. It also explains that optional server options are baked into the returned URL as query parameters, which adds value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence states a specific verb and resource: 'Get the MCP remote server URL for a specific connection ID.' The next sentence clarifies the returned artifact as a ready-to-use, connection-scoped Streamable HTTP MCP endpoint, which distinguishes it from sibling tools like get_unified_connection or list_unified_connections. An agent can select this tool confidently without needing to infer scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides an explicit prerequisite: 'Authenticate with a workspace API key to use this.' It also warns that the URL should be treated as a secret, which is important usage context. It does not explicitly name alternatives or state when not to use this tool, so it falls just short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_issueGet issueARead-onlyIdempotentInspect
Retrieve a single issue by its ID from the connected account. Returns the full issue record. Requires id (obtained from list_unified_issues). Use when you already have the ID; to search or list issues, use list_unified_issues.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the issue to get |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond those annotations by stating that the tool returns "the full issue record" and that the issue comes from "the connected account," which is helpful given there is no output schema. It does not mention not-found or error behavior, but that is a minor gap for a simple read-only fetch.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four short sentences, each earning its place: the action, the return value, the parameter provenance, and the routing rule to the alternative tool. There is no filler, tautology, or restatement of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, read-only get tool, the description covers what it does, what it returns, where the id comes from, and when to use the sibling list tool instead. The absence of an output schema is partially mitigated by stating "Returns the full issue record." It lacks detail on error responses or not-found behavior, but those are unlikely to prevent correct selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the sole parameter already has a clear description, so the baseline is 3. The description adds extra meaning by explaining that the id is obtained from list_unified_issues, which tells the agent it is a previously returned unified issue ID rather than an arbitrary search key. No further format or validation details are needed for a single string ID.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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: "Retrieve a single issue by its ID from the connected account." It also distinguishes this tool from list_unified_issues by making clear that this is ID-based retrieval rather than listing or searching, so an agent can tell them apart without inspecting schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives an explicit condition: "Use when you already have the ID; to search or list issues, use list_unified_issues." It also states the required ID is obtained from list_unified_issues, effectively telling the agent when not to use this tool and which sibling to choose instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_webhookGet webhookARead-onlyIdempotentInspect
Retrieve a single webhook by its ID from the connected account. Returns the full webhook record. Requires id (obtained from list_unified_webhooks). Use when you already have the ID; to search or list webhooks, use list_unified_webhooks.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the webhook to get |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds that the webhook is scoped to the 'connected account' and that a 'full webhook record' is returned, which is useful context beyond the annotations. It does not cover error cases like a missing ID, but that is a minor gap for a simple read tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences front-load the action and return value, then provide usage guidance and the sibling alternative. Every sentence earns its place with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only getter with rich annotations, the description covers the object returned, the source of the ID, and the distinction from the listing alternative. No critical information is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes `id` at 100% coverage, so the baseline is 3. The description adds provenance by telling the agent the ID comes from `list_unified_webhooks`, which is extra meaning beyond the schema definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Retrieve a single webhook by its ID'), names the return value ('full webhook record'), and differentiates itself from list_unified_webhooks. An agent can immediately understand exactly what this tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use this tool when you already have the ID and directs ID lookup to `list_unified_webhooks`. This gives a clear when-to-use and an explicit alternative, leaving no ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_unified_workspace_secretsmanagerGet secrets managerCRead-onlyIdempotentInspect
retrieve secrets manager
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the workspace to get |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds no behavioral details beyond these annotations, such as what happens when the ID is invalid, whether partial data is returned, or any resource existence behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only three words, which is concise but under-specified. It restates the tool name without adding informative context, so it does not earn its place as a useful summary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite a simple one-parameter schema and rich annotations, the description leaves important gaps: it doesn't clarify that the target is the workspace's secrets manager rather than a generic secret, doesn't describe return value behavior, and doesn't mention when to prefer this over the list variant. The schema covers the id parameter, but the overall purpose scope remains ambiguous.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%: the only parameter, id, is described as 'The ID of the workspace to get'. The description adds no extra parameter semantics or format details beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'retrieve secrets manager' is a near-verbatim restatement of the name/title 'get secrets manager' and adds no specifics about the workspace-scoped nature of the resource. It names a resource type, but it is ambiguous ('secrets manager' could be generic) and doesn't differentiate from the many get_* siblings beyond that label.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to call this tool versus list_unified_workspace_secretsmanagers or get_unified_webhook/connection. No context is given about prerequisites, alternatives, or scenarios where this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_apicallsList API callsARead-onlyIdempotentInspect
List apicalls from the connected account. Returns an array of apicall records. Supports filtering by updated_gte, sort, order, external_xref, integration_type, error, connection_id, env, and pagination. Use to browse or search many apicalls; to fetch a single apicall by its ID, use get_unified_apicall.
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| sort | No | ||
| type | No | Filter the results to just this type | |
| error | No | Filter the results for API Calls with errors | |
| limit | No | Maximum number of results to return in one page (default 100) | |
| order | No | ||
| offset | No | Number of results to skip, for pagination (default 0) | |
| webhook_id | No | Filter the results to just this webhook | |
| is_billable | No | Filter the results for only billable API Calls | |
| updated_gte | No | Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| connection_id | No | Filter the results to just this integration | |
| external_xref | No | Filter the results to only those integrations for your user referenced by this value | |
| integration_type | No | Filter the results to just this integration |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the return type ('Returns an array of apicall records') and the connected-account scope. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four short sentences, front-loaded with the core purpose, then return type, filter capabilities, and usage guidance. It contains no fluff and every sentence contributes to effective tool selection and invocation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 13-parameter list tool with no output schema, the description adequately communicates purpose, return array, pagination, and the sibling alternative. It omits a few filters (e.g., type, webhook_id, is_billable), but the schema covers these, so the description remains sufficient for correct use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 77%, slightly below the high threshold, so the schema still carries most parameter meaning. The description enumerates several filters and mentions pagination, but it adds little over the schema's own descriptions; it provides a helpful overview without deep semantic detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List apicalls from the connected account', specifying the verb, resource, and scope. It explicitly distinguishes itself from get_unified_apicall by directing single-ID lookups to that sibling, so an agent can immediately tell which tool to use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use guidance: 'Use to browse or search many apicalls; to fetch a single apicall by its ID, use get_unified_apicall.' This names the alternative and the condition for choosing it, satisfying the when/when-not/alternatives requirement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_connectionsList connectionsARead-onlyIdempotentInspect
List connections from the connected account. Returns an array of connection records. Supports filtering by updated_gte, sort, order, external_xref, categories, env, and pagination. Use to browse or search many connections; to fetch a single connection by its ID, use get_unified_connection.
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| sort | No | ||
| limit | No | Maximum number of results to return in one page (default 100) | |
| order | No | ||
| offset | No | Number of results to skip, for pagination (default 0) | |
| categories | No | Filter the results on these categories | |
| updated_gte | No | Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| external_xref | No | Filter the results to only those integrations for your user referenced by this value |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context beyond annotations: it returns an array of connection records, supports multiple filter dimensions, and supports pagination, which helps an agent anticipate response shape and usage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no filler: action and scope first, return shape second, filtering and usage guidance third. Every sentence earns its place, and the critical sibling distinction is included without bloating the description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core operation, return shape, supported filters, pagination, and the relevant single-record alternative. With zero required parameters and no output schema, this is largely sufficient for an agent to invoke it correctly. Slight gaps remain around the meaning of env and exact pagination mechanics, but these are minor relative to the tool's straightforward list semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 63%, so the schema already documents most parameters. The description enumerates several filterable parameters (updated_gte, sort, order, external_xref, categories, env, pagination) but adds little semantic depth beyond repeating their names; notably, env and sort still lack meaningful explanation. The pagination umbrella term slightly compensates, but meaning is not substantially expanded.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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, 'List connections from the connected account,' which clearly identifies the operation and its scope. It also differentiates itself from the sibling get_unified_connection by explicitly framing this as listing many connections versus fetching a single one by ID.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use this tool ('to browse or search many connections') and names the exact alternative for the single-record case ('to fetch a single connection by its ID, use get_unified_connection'). This leaves no ambiguity about which sibling to choose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_environmentsList environmentsARead-onlyIdempotentInspect
List environments from the connected account. Returns an array of environment records. Use to browse or search many environments; to add a new environment, use create_unified_environment.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds return shape ('array of environment records') and data scope, but it does not disclose pagination behavior or limits, which would be useful for a list endpoint. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences carry distinct value: action/scope, return type, and usage alternative. The most important information is front-loaded, with no redundant or filler wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, unparameterized, read-only list tool, the annotations handle the safety profile and the description provides the return type and key sibling distinction. Nothing essential for a correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so the schema is complete. With no parameters, the description does not need to add parameter-level detail; the 0-parameters baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('List environments') plus the scope ('from the connected account'). It also explicitly distinguishes itself from create_unified_environment, making sibling differentiation clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the agent when to use the tool ('Use to browse or search many environments') and names the exact alternative for adding an environment ('use create_unified_environment'). This gives explicit usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_integrationsList available integrationsARead-onlyIdempotentInspect
List integrations from the connected account. Returns an array of integration records. Supports filtering by updated_gte, categories, summary, active, env, type, and pagination. Use to browse or search many integrations.
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| type | No | Filter the results for only this integration type | |
| limit | No | Maximum number of results to return in one page (default 100) | |
| active | No | Filter the results for only the workspace's active integrations | |
| offset | No | Number of results to skip, for pagination (default 0) | |
| summary | No | ||
| categories | No | Filter the results on these categories | |
| updated_gte | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it 'Returns an array of integration records' and lists supported filters, which goes beyond the annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero waste. The purpose is front-loaded, and the filter list and usage guidance are concise and directly relevant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a list tool with 8 parameters and no output schema, the description provides the essential return type, filter list, and usage context. It does not detail return record structure or pagination mechanics, but the schema covers limit/offset. Overall, it is adequate for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 75%, with 'env' and 'summary' having no schema descriptions. The description lists these filters but does not elaborate on their meaning. For parameters with schema descriptions, it adds little beyond repetition. Thus, it partially compensates but does not fully fill the gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the specific verb and resource: 'List integrations from the connected account.' It also mentions the return type and filter capabilities. The name itself clearly distinguishes it from sibling tools that list other resources (connections, environments, webhooks).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Use to browse or search many integrations,' which gives clear context for when to invoke it. It does not explicitly exclude alternatives or mention single-resource retrieval, but the scope is clear enough given the sibling list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_issuesList issuesARead-onlyIdempotentInspect
List issues from the connected account. Returns an array of issue records. Supports filtering by updated_gte, sort, order, and pagination. Use to browse or search many issues; to fetch a single issue by its ID, use get_unified_issue.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| limit | No | Maximum number of results to return in one page (default 100) | |
| order | No | ||
| offset | No | Number of results to skip, for pagination (default 0) | |
| updated_gte | No | Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the description adds useful context beyond those: the data scope ('connected account'), the return shape ('array of issue records'), and supported filtering/pagination. It does not contradict annotations and adds meaningful behavioral context, though it omits potential auth/rate-limit notes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no filler. It front-loads the core action, then capabilities, then usage guidance and sibling routing. Every sentence contributes value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only list endpoint with no required parameters and no output schema, the description covers purpose, scope, filtering, pagination, and the alternative single-issue tool. It is sufficient for correct invocation, though it does not detail the fields inside each issue record or pagination response metadata.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 60%, so the description has some responsibility to clarify parameters. It mentions updated_gte, sort, order, and pagination, but does not add much meaning beyond the schema's existing enum values and descriptions. It groups the parameters helpfully but does not explain how they interact or clarify the less-described `sort` and `order` semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action and resource: 'List issues from the connected account' and 'Returns an array of issue records.' It also distinguishes itself from the sibling tool by explicitly saying to use `get_unified_issue` for fetching a single issue by ID.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use guidance: 'Use to browse or search many issues' and names the alternative for single-issue retrieval. This gives an agent a clear decision rule without needing to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_webhooksList webhooksARead-onlyIdempotentInspect
List webhooks from the connected account. Returns an array of webhook records. Supports filtering by updated_gte, sort, order, object, integration_type, connection_id, created_lte, env, and pagination. Use to browse or search many webhooks; to fetch a single webhook by its ID, use get_unified_webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| env | No | ||
| sort | No | ||
| limit | No | Maximum number of results to return in one page (default 100) | |
| order | No | ||
| object | No | Filter the results for webhooks for only this object | |
| offset | No | Number of results to skip, for pagination (default 0) | |
| created_lte | No | Return only results whose created date is equal or less to this value | |
| updated_gte | No | Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| connection_id | No | Filter the results to just this integration | |
| integration_type | No | Filter the results to just this integration |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the operation as read-only, open-world, idempotent, and non-destructive. The description adds useful context beyond that by stating the return shape ('Returns an array of webhook records') and the scope ('from the connected account'). It does not mention pagination mechanics or rate limits, but the schema covers pagination parameters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tightly packed sentences: the first states the core action, the second summarizes output and filtering options, and the third provides routing guidance. No filler or redundant repetition of schema details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is sufficient for an agent to invoke the tool: it states the resource scope, output type, available filters, and the sibling tool for single-record access. Pagination and defaults are captured in the schema, and the read-only safety profile is fully covered by annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 70%, and the remaining uncovered parameters (env, sort, order) are mentioned in the description as supported filters but not explicitly explained. The description consolidates the filter options and pagination support, which helps agents recognize the tool's capabilities, but it does not add substantial meaning beyond the schema for most parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the specific action 'List webhooks' and the resource, and explicitly identifies the scope as 'from the connected account'. It also distinguishes itself from `get_unified_webhook` by framing this as browsing/seaching many webhooks rather than fetching a single one.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives direct usage guidance: 'Use to browse or search many webhooks' and explicitly names the alternative for a single webhook lookup: `get_unified_webhook`. This tells the agent when to choose this tool versus its sibling without ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_unified_workspace_secretsmanagersList secrets managersCRead-onlyIdempotentInspect
list secrets managers
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| limit | No | Maximum number of results to return in one page (default 100) | |
| order | No | ||
| offset | No | Number of results to skip, for pagination (default 0) | |
| updated_gte | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds no behavioral context beyond those, such as pagination semantics, default page size, or that it returns all workspace secrets managers. With no output schema, the agent cannot infer what the response looks like.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The phrase is concise but under-specified, adding no informational value beyond the title. There is no front-loaded behavioral or usage context; it is a restatement rather than a useful description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite five optional parameters and no output schema, the description offers no information about result shape, sorting defaults, filtering, or pagination behavior. The annotations and schema cover safety and basic limits, but the description is incomplete for an agent deciding whether a result can be processed correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not explain any of the five parameters. The schema documents limit, offset, and updated_gte partially, but sort and order are left to enum-value inference. The description does not compensate for the 60% schema coverage or clarify updated_gte's filtering role.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus get_unified_workspace_secretsmanager, create_unified_workspace_secretsmanager, or other list tools. There is no mention of conditions such as needing all managers, paginating, or filtering, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
remove_unified_connectionDelete connectionADestructiveIdempotentInspect
Delete a connection by its ID from the connected account. Requires id. Permanently removes the record and cannot be undone. To fetch a single connection by its ID, use get_unified_connection.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the connection to remove |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states that deletion is permanent and cannot be undone, adding meaningful context beyond the destructiveHint annotation. It also mentions 'from the connected account', giving scope. No contradiction with annotations (idempotentHint is not contradicted). The permanence disclosure is valuable but the description could also mention the idempotent nature, though that is already in annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The core action is front-loaded, and the alternative is stated efficiently. Every word contributes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation with one parameter and no output schema, the description is quite complete. It explains the destructive side effect and routes to the correct sibling. It doesn't detail error handling or idempotency, but those are minor given the annotations and simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'id', which is fully documented. The description simply repeats that 'id' is required, adding no new semantics beyond what the schema already provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (delete) and resource (connection), specifies that it operates by ID, and explicitly distinguishes it from the get_unified_connection sibling. An agent can immediately understand what the tool does and how it differs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly instructs to use this tool for deletion and names the alternative (get_unified_connection) for fetching a connection by ID. This provides clear when-to-use and when-not-to-use guidance, though it doesn't contrast with other remove_* tools, it sufficiently differentiates from the most relevant sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
remove_unified_environmentDelete environmentADestructiveIdempotentInspect
Delete an environment by its ID from the connected account. Requires id. Permanently removes the record and cannot be undone. To search or list environments, use list_unified_environments.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the environment to remove |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the operation as destructive and non-read-only. The description adds beyond that by stating the removal is permanent and cannot be undone, and by clarifying it operates on the connected account. It doesn't cover downstream side effects, but the added context is substantive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences each earn their place: the action and target, the required parameter, the permanent consequence, and the routing to the list alternative. It is front-loaded and free of filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter destructive tool with annotations covering safety and no output schema, the description is complete. It covers what the tool does, the required input, the irreversibility, and the correct sibling for non-destructive queries.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the property description already explains that `id` is the environment to remove. The description only repeats 'Requires id' without adding extra format, constraints, or behavioral nuance, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Delete') and resource ('environment by its ID'), plus the scope ('from the connected account'). It clearly distinguishes this from the list/search sibling by naming `list_unified_environments` as the alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says when to use this tool (delete by ID) and directs search/list needs to `list_unified_environments`. This provides clear routing versus the most relevant sibling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
remove_unified_webhookDelete webhookADestructiveIdempotentInspect
Delete a webhook by its ID from the connected account. Requires id. Permanently removes the record and cannot be undone. To fetch a single webhook by its ID, use get_unified_webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the webhook to remove |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare `destructiveHint: true`, but the description adds specificity: 'permanently removes' and 'cannot be undone' reinforce the irreversibility. It also clarifies scope ('from the connected account'), which is not in the annotations. This goes beyond mere repetition of the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The core action is front-loaded, the destructive caveat is stated early, and the alternative is mentioned in the second sentence. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter destructive tool with no output schema, the description is complete: it explains the action, the requirement, the consequence, and the alternative. Nothing needed for correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, so the `id` parameter is already fully documented. The description merely restates 'Requires id' without adding new meaning, syntax, or edge cases. This meets the baseline for high schema coverage but adds no extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Delete a webhook by its ID') and clearly distinguishes itself from fetching via `get_unified_webhook`. It is immediately clear what this tool does and how it differs from its sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the required parameter (`Requires id`), the destructive consequence ('Permanently removes the record and cannot be undone'), and explicitly points to the alternative tool for fetching (`get_unified_webhook`). This gives clear when-to-use and when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
remove_unified_workspace_secretsmanagerDelete secrets managerDDestructiveIdempotentInspect
remove secrets manager
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the workspace to remove |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds nothing beyond that. It does not disclose any side effects, what happens to associated resources, or whether confirmation is needed. The description carries no behavioral information beyond what the annotations already provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but this is under-specification rather than conciseness. The single sentence is a tautology that does not earn its place. It adds no value and fails to provide necessary context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with one parameter and no output schema, the description should explain what the removal entails, any irreversible effects, and whether there are dependencies. None of this is present. The description is completely inadequate for an agent to safely and correctly invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter 'id' is already documented as 'The ID of the workspace to remove'. The description does not add any additional meaning or clarify the relationship between the secrets manager and the workspace. Per the baseline rule for high coverage, a score of 3 is appropriate, though the description could have clarified the parameter's role.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'remove secrets manager' is a tautology that restates the tool name and title without adding any specificity. It does not distinguish this tool from its siblings like remove_unified_connection or remove_unified_environment, and it does not clarify what 'secrets manager' refers to in the context of a workspace.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus the other remove_* tools. No mention of prerequisites, conditions, or alternatives. An agent would have to infer usage purely from the name and schema, which is not sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_docsSearch Unified.to documentationARead-onlyIdempotentInspect
Search the Unified.to API and MCP documentation (https://docs.unified.to) and return an answer with citations for a free-form question.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The query to search the documents |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds value by disclosing that the tool returns an answer with citations, which is behavioral context beyond the annotations. It doesn't mention rate limits or result limits, but the openWorldHint and readOnlyHint cover the main behavioral concerns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the action and resource, then adds the key behavioral detail (answer with citations). Every word earns its place, and there is no redundancy with the title or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with one parameter, full annotation coverage, and no output schema, the description is nearly complete. It tells the agent what it does, what it returns, and the URL of the documentation. The only minor gap is not specifying the format of the answer or any limitations, but these are not critical for a read-only search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents the single 'query' parameter. The description adds that the query is 'free-form' and that the answer includes citations, which slightly enriches the parameter semantics. However, it doesn't add format or syntax details beyond what the schema provides, so the baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: searching Unified.to API and MCP documentation and returning an answer with citations for a free-form question. It specifies the resource (docs.unified.to) and the action (search and return an answer), making it distinct from sibling tools that manage connections, webhooks, or environments.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for free-form questions about Unified.to documentation, which is clear context. It doesn't explicitly state when not to use it or name alternatives, but given the sibling tools are all CRUD operations for resources, the usage context is sufficiently clear without needing exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
update_unified_connectionUpdate connectionADestructiveIdempotentInspect
Update an existing connection by its ID in the connected account. Returns the updated connection record. Requires id and the fields to change in the request body. Modifies an existing record; to add a new connection, use create_unified_connection.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the connection to update | |
| auth | No | An authentication object that represents a specific authorized user's connection to an integration | |
| is_paused | No | Whether this integration has exceed the monthly limit of the plan | |
| categories | Yes | The Integration categories that this connection supports | |
| environment | No | ||
| permissions | Yes | Array | |
| workspace_id | No | (reference to KmsSpace) | |
| external_xref | No | customer's user ID | |
| last_healthy_at | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| integration_name | No | ||
| integration_type | Yes | The integration type | |
| last_unhealthy_at | No | (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| secretsmanager_id | No | the ID of the SecretsManager object | |
| secretsmanager_key | No | the key/path/name of the secret within the vault | |
| last_unhealthy_code | No | The HTTP status code that caused the last unhealthy status |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that it modifies an existing record and returns the updated connection record. Since annotations already flag destructiveHint=true and idempotentHint=true, the description adds value by specifying the return behavior and the modification target, which is useful context beyond the structured annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no filler. The core action is front-loaded, followed by the return value and the pointer to the create sibling. Every sentence earns its place, making it easy to scan and extract the essential information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex tool with 15 params, nested objects, and no output schema, the description is sparse. It correctly mentions the return value and the create alternative, but it omits that `integration_type`, `permissions`, and `categories` are required by the schema even for updates, which could mislead an agent into sending only `id` and a subset of fields. This is a notable gap for a mutation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is high (87%), so most parameters are already described. The description adds only that `id` and fields to change are required, which is a general statement. It does not explain which fields are updatable or how the auth object relates to the update, so it stays at the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: 'Update an existing connection by its ID' with a specific resource and verb. It distinguishes itself from `create_unified_connection` by explicitly noting that adding a new connection should use that sibling. This is precise and leaves no ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells agents when to use this tool versus `create_unified_connection` by contrasting 'modifies an existing record' with 'to add a new connection'. It also states prerequisites: requires `id` and fields to change in the request body. This is direct when/when-not guidance with a named alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
update_unified_webhookUpdate webhookBDestructiveIdempotentInspect
Update an existing webhook by its ID in the connected account. Returns the updated webhook record. Requires id and the fields to change in the request body. Modifies an existing record; to add a new webhook, use create_unified_webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the webhook to update | |
| meta | No | ||
| runs | No | An array of the most revent virtual webhook runs | |
| event | Yes | ||
| db_url | No | ||
| fields | No | ||
| db_type | No | ||
| filters | No | ||
| is_beta | No | ||
| hook_url | No | The URL of the webhook | |
| interval | No | The interval (in minutes) to check for updated/new objets | |
| db_schema | No | ||
| is_paused | No | ||
| checked_at | No | The last date/time that a check was done on this object (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) | |
| is_healthy | No | ||
| environment | No | ||
| object_type | Yes | The object to return (eg | |
| webhook_type | No | ||
| workspace_id | No | (reference to KmsSpace) | |
| connection_id | Yes | ||
| db_name_prefix | No | ||
| page_max_limit | No | ||
| integration_type | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose destructive and non-read-only behavior. The description adds that it returns the updated webhook record and points to create_unified_webhook for new records, which is useful. However, the claim 'Requires `id` and the fields to change' inaccurately reflects the required parameters in the schema (id, connection_id, object_type, event), misrepresenting the invocation constraints. It does not contradict annotations, hence score 3.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core action and outcome. It is efficient with no filler, but the 'Requires id and fields' part is slightly redundant and could be clearer. Overall it is well-structured and appropriately sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (23 parameters, 4 required, no output schema, nested objects), the description is far from sufficient. It does not explain the request body structure, the meaning of required fields beyond id, the expected response format, or the scope (connected account). It also fails to address potential edge cases like partial updates or idempotency. The description is a minimal skeleton for a complex update operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With only 30% schema description coverage and 23 parameters, the description does not compensate. It only mentions 'id and the fields to change' without clarifying that connection_id, object_type, and event are required, nor what the many optional parameters mean or how they affect the update. The description adds almost no semantic value for parameter usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (update), the resource (webhook), identifies it by ID, and explicitly contrasts with create_unified_webhook for new webhooks. It is specific and distinguishes this tool from its create sibling, leaving no ambiguity about its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides a clear alternative (create_unified_webhook) for new webhooks, which is the primary usage distinction. However, it does not mention other closely related siblings like update_unified_webhook_trigger, nor does it explain when to use this tool versus alternative update mechanisms. The guidance is adequate but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
update_unified_webhook_triggerTrigger webhookCDestructiveInspect
trigger webhook
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The ID of the webhook to update |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate destructiveHint=true and idempotentHint=false, but the description adds no behavioral context beyond what annotations already provide. It does not explain what side effects triggering a webhook has, whether it sends a test event, or what happens to the webhook configuration. The description does not contradict annotations, but it fails to disclose the destructive nature implied by the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short ('trigger webhook'), which is concise but under-specified. It does not earn its place because it merely repeats the tool name and title without adding any useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive, non-idempotent tool with no output schema, the description is inadequate. It does not explain what triggering a webhook does, what the side effects are, or what the agent should expect after calling it. The single parameter is documented, but the behavioral context is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single 'id' parameter, so the schema already documents the parameter. The description adds no additional meaning about the id's role or format, but with full coverage the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tautological: description restates name/title.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus update_unified_webhook or create_unified_webhook. The description does not state any context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
9 tool updates
- Changed
create_unified_connection2 fields changed- added
Input schema / properties / last_unhealthy_codeAdded value: +{ + "description": "The HTTP status code that caused the last unhealthy status", + "type": "number" +} - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_vendorcredit_read", - "accounting_vendorcredit_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "commerce_reservation_read", - "commerce_reservation_write", - "commerce_availability_read", - "commerce_availability_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "crm_picklist_read", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "hris_document_read", - "hris_document_write", - "hris_taxonomy_read", - "hris_taxonomy_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_channel_write", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "ads_target_read", - "ads_promoted_read", - "analytics_property_read", - "analytics_property_write", - "analytics_event_read", - "analytics_event_write", - "analytics_session_read", - "analytics_visitor_read", - "analytics_visitor_write", - "analytics_report_read", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read", - "signing_document_read", - "signing_document_write", - "signing_signatory_read", - "signing_signatory_write", - "signing_template_read", - "clubs_group_read", - "clubs_group_write", - "clubs_member_read", - "clubs_member_write", - "clubs_activity_read", - "clubs_activity_write", - "clubs_location_read", - "clubs_location_write", - "clubs_event_read", - "clubs_event_write", - "datastore_database_read", - "datastore_database_write", - "datastore_table_read", - "datastore_table_write", - "datastore_record_read", - "datastore_record_write", - "datastore_query_read", - "datastore_query_write", - "cdp_profile_read", - "cdp_profile_write", - "cdp_segment_read", - "cdp_segment_write", - "cdp_event_read", - "cdp_event_write", - "cdp_source_read", - "cdp_source_write", - "cdp_destination_read", - "cdp_destination_write", - "cdp_activation_read", - "cdp_activation_write" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_vendorcredit_read", + "accounting_vendorcredit_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "hris_document_read", + "hris_document_write", + "hris_taxonomy_read", + "hris_taxonomy_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write", + "cdp_profile_read", + "cdp_profile_write", + "cdp_segment_read", + "cdp_segment_write", + "cdp_event_read", + "cdp_event_write", + "cdp_source_read", + "cdp_source_write", + "cdp_destination_read", + "cdp_destination_write", + "cdp_activation_read", + "cdp_activation_write" +]
- Changed
get_unified_connection_mcp_url1 field changed- removed
Input schema / properties / dcRemoved value: -{ - "description": "Preferred data center / region for the generated URL", - "enum": [ - "us", - "eu", - "au", - "dev" - ], - "type": "string" -}
- Changed
list_unified_apicalls2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
list_unified_connections2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
list_unified_integrations2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
list_unified_issues2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
list_unified_webhooks2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
list_unified_workspace_secretsmanagers2 fields changed- added
Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return in one page (default 100)" - added
Input schema / properties / offset / descriptionAdded value: +"Number of results to skip, for pagination (default 0)"
- Changed
update_unified_connection2 fields changed- added
Input schema / properties / last_unhealthy_codeAdded value: +{ + "description": "The HTTP status code that caused the last unhealthy status", + "type": "number" +} - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_vendorcredit_read", - "accounting_vendorcredit_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "commerce_reservation_read", - "commerce_reservation_write", - "commerce_availability_read", - "commerce_availability_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "crm_picklist_read", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "hris_document_read", - "hris_document_write", - "hris_taxonomy_read", - "hris_taxonomy_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_channel_write", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "ads_target_read", - "ads_promoted_read", - "analytics_property_read", - "analytics_property_write", - "analytics_event_read", - "analytics_event_write", - "analytics_session_read", - "analytics_visitor_read", - "analytics_visitor_write", - "analytics_report_read", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read", - "signing_document_read", - "signing_document_write", - "signing_signatory_read", - "signing_signatory_write", - "signing_template_read", - "clubs_group_read", - "clubs_group_write", - "clubs_member_read", - "clubs_member_write", - "clubs_activity_read", - "clubs_activity_write", - "clubs_location_read", - "clubs_location_write", - "clubs_event_read", - "clubs_event_write", - "datastore_database_read", - "datastore_database_write", - "datastore_table_read", - "datastore_table_write", - "datastore_record_read", - "datastore_record_write", - "datastore_query_read", - "datastore_query_write", - "cdp_profile_read", - "cdp_profile_write", - "cdp_segment_read", - "cdp_segment_write", - "cdp_event_read", - "cdp_event_write", - "cdp_source_read", - "cdp_source_write", - "cdp_destination_read", - "cdp_destination_write", - "cdp_activation_read", - "cdp_activation_write" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_vendorcredit_read", + "accounting_vendorcredit_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "hris_document_read", + "hris_document_write", + "hris_taxonomy_read", + "hris_taxonomy_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write", + "cdp_profile_read", + "cdp_profile_write", + "cdp_segment_read", + "cdp_segment_write", + "cdp_event_read", + "cdp_event_write", + "cdp_source_read", + "cdp_source_write", + "cdp_destination_read", + "cdp_destination_write", + "cdp_activation_read", + "cdp_activation_write" +]
7 tool updates
- Changed
create_unified_connection2 fields changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "analytics", - "forms", - "shipping", - "assessment", - "signing", - "clubs", - "datastore" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore", + "cdp" +] - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "commerce_reservation_read", - "commerce_reservation_write", - "commerce_availability_read", - "commerce_availability_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "crm_picklist_read", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "ads_target_read", - "ads_promoted_read", - "analytics_property_read", - "analytics_property_write", - "analytics_event_read", - "analytics_event_write", - "analytics_session_read", - "analytics_visitor_read", - "analytics_visitor_write", - "analytics_report_read", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read", - "signing_document_read", - "signing_document_write", - "signing_signatory_read", - "signing_signatory_write", - "signing_template_read", - "clubs_group_read", - "clubs_group_write", - "clubs_member_read", - "clubs_member_write", - "clubs_activity_read", - "clubs_activity_write", - "clubs_location_read", - "clubs_location_write", - "clubs_event_read", - "clubs_event_write", - "datastore_database_read", - "datastore_database_write", - "datastore_table_read", - "datastore_table_write", - "datastore_record_read", - "datastore_record_write", - "datastore_query_read", - "datastore_query_write" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_vendorcredit_read", + "accounting_vendorcredit_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "hris_document_read", + "hris_document_write", + "hris_taxonomy_read", + "hris_taxonomy_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_channel_write", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write", + "cdp_profile_read", + "cdp_profile_write", + "cdp_segment_read", + "cdp_segment_write", + "cdp_event_read", + "cdp_event_write", + "cdp_source_read", + "cdp_source_write", + "cdp_destination_read", + "cdp_destination_write", + "cdp_activation_read", + "cdp_activation_write" +]
- Changed
create_unified_webhook1 field changed- changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "commerce_reservation", - "commerce_availability", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "crm_picklist", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "ads_target", - "ads_promoted", - "analytics_property", - "analytics_event", - "analytics_session", - "analytics_visitor", - "analytics_report", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking", - "signing_document", - "signing_signatory", - "signing_template", - "clubs_group", - "clubs_member", - "clubs_activity", - "clubs_location", - "clubs_event", - "datastore_database", - "datastore_table", - "datastore_record", - "datastore_query" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_vendorcredit", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "hris_document", + "hris_taxonomy", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query", + "cdp_profile", + "cdp_segment", + "cdp_event", + "cdp_source", + "cdp_destination", + "cdp_activation" +]
- Changed
list_unified_connections1 field changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "analytics", - "forms", - "shipping", - "assessment", - "signing", - "clubs", - "datastore" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore", + "cdp" +]
- Changed
list_unified_integrations1 field changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "analytics", - "forms", - "shipping", - "assessment", - "signing", - "clubs", - "datastore" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore", + "cdp" +]
- Changed
list_unified_webhooks1 field changed- changed
Input schema / properties / object / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "commerce_reservation", - "commerce_availability", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "crm_picklist", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "ads_target", - "ads_promoted", - "analytics_property", - "analytics_event", - "analytics_session", - "analytics_visitor", - "analytics_report", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking", - "signing_document", - "signing_signatory", - "signing_template", - "clubs_group", - "clubs_member", - "clubs_activity", - "clubs_location", - "clubs_event", - "datastore_database", - "datastore_table", - "datastore_record", - "datastore_query" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_vendorcredit", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "hris_document", + "hris_taxonomy", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query", + "cdp_profile", + "cdp_segment", + "cdp_event", + "cdp_source", + "cdp_destination", + "cdp_activation" +]
- Changed
update_unified_connection2 fields changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "analytics", - "forms", - "shipping", - "assessment", - "signing", - "clubs", - "datastore" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore", + "cdp" +] - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "commerce_reservation_read", - "commerce_reservation_write", - "commerce_availability_read", - "commerce_availability_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "crm_picklist_read", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "ads_target_read", - "ads_promoted_read", - "analytics_property_read", - "analytics_property_write", - "analytics_event_read", - "analytics_event_write", - "analytics_session_read", - "analytics_visitor_read", - "analytics_visitor_write", - "analytics_report_read", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read", - "signing_document_read", - "signing_document_write", - "signing_signatory_read", - "signing_signatory_write", - "signing_template_read", - "clubs_group_read", - "clubs_group_write", - "clubs_member_read", - "clubs_member_write", - "clubs_activity_read", - "clubs_activity_write", - "clubs_location_read", - "clubs_location_write", - "clubs_event_read", - "clubs_event_write", - "datastore_database_read", - "datastore_database_write", - "datastore_table_read", - "datastore_table_write", - "datastore_record_read", - "datastore_record_write", - "datastore_query_read", - "datastore_query_write" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_vendorcredit_read", + "accounting_vendorcredit_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "hris_document_read", + "hris_document_write", + "hris_taxonomy_read", + "hris_taxonomy_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_channel_write", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write", + "cdp_profile_read", + "cdp_profile_write", + "cdp_segment_read", + "cdp_segment_write", + "cdp_event_read", + "cdp_event_write", + "cdp_source_read", + "cdp_source_write", + "cdp_destination_read", + "cdp_destination_write", + "cdp_activation_read", + "cdp_activation_write" +]
- Changed
update_unified_webhook1 field changed- changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "commerce_reservation", - "commerce_availability", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "crm_picklist", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "ads_target", - "ads_promoted", - "analytics_property", - "analytics_event", - "analytics_session", - "analytics_visitor", - "analytics_report", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking", - "signing_document", - "signing_signatory", - "signing_template", - "clubs_group", - "clubs_member", - "clubs_activity", - "clubs_location", - "clubs_event", - "datastore_database", - "datastore_table", - "datastore_record", - "datastore_query" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_vendorcredit", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "hris_document", + "hris_taxonomy", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query", + "cdp_profile", + "cdp_segment", + "cdp_event", + "cdp_source", + "cdp_destination", + "cdp_activation" +]
12 tool updates
- Changed
create_unified_connection9 fields changed- added
Input schema / properties / auth / properties / audienceAdded value: +{ + "type": "string" +} - removed
Input schema / properties / auth_aws_arnRemoved value: -{ - "description": "the AWS ARN / secretID for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_azure_keyvault_idRemoved value: -{ - "description": "the Azure Key Vault ID for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_gcp_secret_nameRemoved value: -{ - "description": "the Google Cloud Secret Manager name for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_hashi_vault_pathRemoved value: -{ - "description": "the HashiCorp Vault path for the stored auth field", - "type": "string" -} - changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "forms", - "shipping", - "assessment" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore" +] - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write" +] - added
Input schema / properties / secretsmanager_idAdded value: +{ + "description": "the ID of the SecretsManager object", + "type": "string" +} - added
Input schema / properties / secretsmanager_keyAdded value: +{ + "description": "the key/path/name of the secret within the vault", + "type": "string" +}
- Changed
create_unified_webhook3 fields changed- changed
Input schema / properties / db_type / enumPrevious value: -[ - "mongodb", - "mysql", - "postgres", - "mssql", - "mariadb", - "supabase" -]New value: +[ + "mongodb", + "mysql", + "postgres", + "mssql", + "mariadb", + "supabase", + "snowflake" +] - added
Input schema / properties / is_betaAdded value: +{ + "type": "boolean" +} - changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query" +]
- Added
create_unified_workspace_secretsmanager - Added
get_unified_workspace_secretsmanager - Changed
list_unified_connections1 field changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "forms", - "shipping", - "assessment" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore" +]
- Changed
list_unified_integrations1 field changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "forms", - "shipping", - "assessment" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore" +]
- Changed
list_unified_webhooks1 field changed- changed
Input schema / properties / object / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query" +]
- Added
list_unified_workspace_secretsmanagers - Added
remove_unified_workspace_secretsmanager - Added
search_docs - Changed
update_unified_connection9 fields changed- added
Input schema / properties / auth / properties / audienceAdded value: +{ + "type": "string" +} - removed
Input schema / properties / auth_aws_arnRemoved value: -{ - "description": "the AWS ARN / secretID for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_azure_keyvault_idRemoved value: -{ - "description": "the Azure Key Vault ID for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_gcp_secret_nameRemoved value: -{ - "description": "the Google Cloud Secret Manager name for the stored auth field", - "type": "string" -} - removed
Input schema / properties / auth_hashi_vault_pathRemoved value: -{ - "description": "the HashiCorp Vault path for the stored auth field", - "type": "string" -} - changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification", - "ads", - "forms", - "shipping", - "assessment" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "analytics", + "forms", + "shipping", + "assessment", + "signing", + "clubs", + "datastore" +] - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "accounting_cashflow_read", - "accounting_cashflow_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "commerce_saleschannel_read", - "commerce_saleschannel_write", - "commerce_itemvariant_read", - "commerce_itemvariant_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "assessment_package_read", - "assessment_package_write", - "assessment_order_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "martech_campaign_read", - "martech_campaign_write", - "martech_report_read", - "martech_report_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "hris_deduction_read", - "hris_deduction_write", - "hris_benefit_read", - "hris_benefit_write", - "hris_bankaccount_read", - "hris_bankaccount_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "messaging_event_read", - "messaging_event_write", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "lms_content_read", - "lms_content_write", - "lms_collection_read", - "lms_collection_write", - "lms_activity_read", - "lms_activity_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "calendar_webinar_read", - "calendar_webinar_write", - "enrich_person_read", - "enrich_company_read", - "ads_ad_read", - "ads_ad_write", - "ads_campaign_read", - "ads_campaign_write", - "ads_group_read", - "ads_group_write", - "ads_report_read", - "ads_organization_read", - "ads_organization_write", - "ads_creative_read", - "ads_creative_write", - "ads_insertionorder_read", - "ads_insertionorder_write", - "forms_form_read", - "forms_form_write", - "forms_submission_read", - "forms_submission_write", - "shipping_shipment_read", - "shipping_shipment_write", - "shipping_label_read", - "shipping_label_write", - "shipping_tracking_read", - "shipping_rate_read", - "shipping_carrier_read" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "commerce_reservation_read", + "commerce_reservation_write", + "commerce_availability_read", + "commerce_availability_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "crm_picklist_read", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "ads_target_read", + "ads_promoted_read", + "analytics_property_read", + "analytics_property_write", + "analytics_event_read", + "analytics_event_write", + "analytics_session_read", + "analytics_visitor_read", + "analytics_visitor_write", + "analytics_report_read", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read", + "signing_document_read", + "signing_document_write", + "signing_signatory_read", + "signing_signatory_write", + "signing_template_read", + "clubs_group_read", + "clubs_group_write", + "clubs_member_read", + "clubs_member_write", + "clubs_activity_read", + "clubs_activity_write", + "clubs_location_read", + "clubs_location_write", + "clubs_event_read", + "clubs_event_write", + "datastore_database_read", + "datastore_database_write", + "datastore_table_read", + "datastore_table_write", + "datastore_record_read", + "datastore_record_write", + "datastore_query_read", + "datastore_query_write" +] - added
Input schema / properties / secretsmanager_idAdded value: +{ + "description": "the ID of the SecretsManager object", + "type": "string" +} - added
Input schema / properties / secretsmanager_keyAdded value: +{ + "description": "the key/path/name of the secret within the vault", + "type": "string" +}
- Changed
update_unified_webhook3 fields changed- changed
Input schema / properties / db_type / enumPrevious value: -[ - "mongodb", - "mysql", - "postgres", - "mssql", - "mariadb", - "supabase" -]New value: +[ + "mongodb", + "mysql", + "postgres", + "mssql", + "mariadb", + "supabase", + "snowflake" +] - added
Input schema / properties / is_betaAdded value: +{ + "type": "boolean" +} - changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "accounting_cashflow", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "commerce_saleschannel", - "commerce_itemvariant", - "verification_package", - "verification_request", - "assessment_package", - "assessment_order", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "hris_deduction", - "hris_benefit", - "hris_bankaccount", - "martech_list", - "martech_member", - "martech_campaign", - "martech_report", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "messaging_event", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "lms_content", - "lms_collection", - "lms_activity", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording", - "calendar_webinar", - "ads_organization", - "ads_ad", - "ads_campaign", - "ads_report", - "ads_group", - "ads_creative", - "ads_insertionorder", - "forms_form", - "forms_submission", - "shipping_carrier", - "shipping_rate", - "shipping_shipment", - "shipping_label", - "shipping_tracking" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "commerce_reservation", + "commerce_availability", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "crm_picklist", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "ads_target", + "ads_promoted", + "analytics_property", + "analytics_event", + "analytics_session", + "analytics_visitor", + "analytics_report", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking", + "signing_document", + "signing_signatory", + "signing_template", + "clubs_group", + "clubs_member", + "clubs_activity", + "clubs_location", + "clubs_event", + "datastore_database", + "datastore_table", + "datastore_record", + "datastore_query" +]
1 tool update
- Added
get_unified_connection_mcp_url
19 tool updates
- Changed
create_unified_connection10 fields changed- added
Input schema / properties / auth / properties / user_id / descriptionAdded value: +"(reference to HrisEmployee)" - added
Input schema / properties / auth_azure_keyvault_idAdded value: +{ + "description": "the Azure Key Vault ID for the stored auth field", + "type": "string" +} - added
Input schema / properties / auth_gcp_secret_nameAdded value: +{ + "description": "the Google Cloud Secret Manager name for the stored auth field", + "type": "string" +} - added
Input schema / properties / auth_hashi_vault_pathAdded value: +{ + "description": "the HashiCorp Vault path for the stored auth field", + "type": "string" +} - changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "forms", + "shipping", + "assessment" +] - removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - added
Input schema / properties / last_healthy_at / descriptionAdded value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - added
Input schema / properties / last_unhealthy_at / descriptionAdded value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "enrich_person_read", - "enrich_company_read" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read" +] - added
Input schema / properties / workspace_id / descriptionAdded value: +"(reference to KmsSpace)"
- Added
create_unified_environment - Changed
create_unified_webhook4 fields changed- changed
Input schema / properties / checked_at / descriptionPrevious value: -"The last date/time that a check was done on this object"New value: +"The last date/time that a check was done on this object (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - changed
Input schema / properties / db_type / enumPrevious value: -[ - "mongodb", - "mysql", - "postgres", - "mssql", - "mariadb" -]New value: +[ + "mongodb", + "mysql", + "postgres", + "mssql", + "mariadb", + "supabase" +] - changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "verification_package", - "verification_request", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "martech_list", - "martech_member", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking" +] - added
Input schema / properties / workspace_id / descriptionAdded value: +"(reference to KmsSpace)"
- Changed
get_unified_apicall1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Changed
get_unified_connection1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Changed
get_unified_issue1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Changed
get_unified_webhook1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Changed
list_unified_apicalls3 fields changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - changed
Input schema / properties / type / enumPrevious value: -[ - "login", - "webhook", - "inbound" -]New value: +[ + "login", + "webhook", + "inbound", + "mcp" +] - changed
Input schema / properties / updated_gte / descriptionPrevious value: -"Return only results whose updated date is equal or greater to this value"New value: +"Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"
- Changed
list_unified_connections3 fields changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "forms", + "shipping", + "assessment" +] - removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - changed
Input schema / properties / updated_gte / descriptionPrevious value: -"Return only results whose updated date is equal or greater to this value"New value: +"Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"
- Added
list_unified_environments - Changed
list_unified_integrations3 fields changed- changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "forms", + "shipping", + "assessment" +] - removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - added
Input schema / properties / updated_gte / descriptionAdded value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"
- Changed
list_unified_issues2 fields changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - changed
Input schema / properties / updated_gte / descriptionPrevious value: -"Return only results whose updated date is equal or greater to this value"New value: +"Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"
- Changed
list_unified_webhooks3 fields changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - changed
Input schema / properties / object / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "verification_package", - "verification_request", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "martech_list", - "martech_member", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking" +] - changed
Input schema / properties / updated_gte / descriptionPrevious value: -"Return only results whose updated date is equal or greater to this value"New value: +"Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"
- Changed
remove_unified_connection1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Added
remove_unified_environment - Changed
remove_unified_webhook1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
- Changed
update_unified_connection10 fields changed- added
Input schema / properties / auth / properties / user_id / descriptionAdded value: +"(reference to HrisEmployee)" - added
Input schema / properties / auth_azure_keyvault_idAdded value: +{ + "description": "the Azure Key Vault ID for the stored auth field", + "type": "string" +} - added
Input schema / properties / auth_gcp_secret_nameAdded value: +{ + "description": "the Google Cloud Secret Manager name for the stored auth field", + "type": "string" +} - added
Input schema / properties / auth_hashi_vault_pathAdded value: +{ + "description": "the HashiCorp Vault path for the stored auth field", + "type": "string" +} - changed
Input schema / properties / categories / items / enumPrevious value: -[ - "passthrough", - "hris", - "ats", - "auth", - "crm", - "enrich", - "martech", - "ticketing", - "uc", - "accounting", - "storage", - "commerce", - "payment", - "genai", - "messaging", - "kms", - "task", - "scim", - "lms", - "repo", - "metadata", - "calendar", - "verification" -]New value: +[ + "passthrough", + "hris", + "ats", + "auth", + "crm", + "enrich", + "martech", + "ticketing", + "uc", + "accounting", + "storage", + "commerce", + "payment", + "genai", + "messaging", + "kms", + "task", + "scim", + "lms", + "repo", + "metadata", + "calendar", + "verification", + "ads", + "forms", + "shipping", + "assessment" +] - removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -} - added
Input schema / properties / last_healthy_at / descriptionAdded value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - added
Input schema / properties / last_unhealthy_at / descriptionAdded value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - changed
Input schema / properties / permissions / items / enumPrevious value: -[ - "accounting_account_read", - "accounting_account_write", - "accounting_transaction_read", - "accounting_transaction_write", - "accounting_journal_read", - "accounting_journal_write", - "accounting_invoice_read", - "accounting_invoice_write", - "accounting_bill_read", - "accounting_bill_write", - "accounting_creditmemo_read", - "accounting_creditmemo_write", - "accounting_contact_read", - "accounting_contact_write", - "accounting_expense_read", - "accounting_expense_write", - "accounting_taxrate_read", - "accounting_taxrate_write", - "accounting_organization_read", - "accounting_order_read", - "accounting_order_write", - "accounting_purchaseorder_read", - "accounting_purchaseorder_write", - "accounting_salesorder_read", - "accounting_salesorder_write", - "accounting_report_read", - "accounting_report_write", - "accounting_trialbalance_read", - "accounting_trialbalance_write", - "accounting_profitloss_read", - "accounting_profitloss_write", - "accounting_balancesheet_read", - "accounting_balancesheet_write", - "accounting_category_read", - "accounting_category_write", - "payment_payment_read", - "payment_payment_write", - "payment_payout_read", - "payment_refund_read", - "payment_link_read", - "payment_link_write", - "payment_subscription_read", - "payment_subscription_write", - "commerce_item_read", - "commerce_item_write", - "commerce_collection_read", - "commerce_collection_write", - "commerce_inventory_read", - "commerce_inventory_write", - "commerce_location_read", - "commerce_location_write", - "commerce_review_read", - "commerce_review_write", - "verification_package_read", - "verification_request_read", - "verification_request_write", - "ats_activity_read", - "ats_activity_write", - "ats_application_read", - "ats_application_write", - "ats_applicationstatus_read", - "ats_candidate_read", - "ats_candidate_write", - "ats_interview_read", - "ats_interview_write", - "ats_job_read", - "ats_job_write", - "ats_company_read", - "ats_company_write", - "ats_document_read", - "ats_document_write", - "ats_scorecard_read", - "ats_scorecard_write", - "crm_company_read", - "crm_company_write", - "crm_contact_read", - "crm_contact_write", - "crm_deal_read", - "crm_deal_write", - "crm_event_read", - "crm_event_write", - "crm_lead_read", - "crm_lead_write", - "crm_pipeline_read", - "crm_pipeline_write", - "martech_list_read", - "martech_list_write", - "martech_member_read", - "martech_member_write", - "ticketing_customer_read", - "ticketing_customer_write", - "ticketing_ticket_read", - "ticketing_ticket_write", - "ticketing_note_read", - "ticketing_note_write", - "ticketing_category_read", - "ticketing_category_write", - "hris_employee_read", - "hris_employee_write", - "hris_group_read", - "hris_group_write", - "hris_payslip_read", - "hris_payslip_write", - "hris_timeoff_read", - "hris_timeoff_write", - "hris_timeshift_read", - "hris_timeshift_write", - "hris_company_read", - "hris_company_write", - "hris_location_read", - "hris_location_write", - "hris_device_read", - "hris_device_write", - "uc_call_read", - "uc_contact_read", - "uc_contact_write", - "uc_comment_read", - "uc_comment_write", - "uc_recording_read", - "storage_file_read", - "storage_file_write", - "webhook", - "genai_model_read", - "genai_prompt_read", - "genai_prompt_write", - "genai_embedding_read", - "genai_embedding_write", - "messaging_message_read", - "messaging_message_write", - "messaging_channel_read", - "kms_space_read", - "kms_space_write", - "kms_page_read", - "kms_page_write", - "kms_comment_read", - "kms_comment_write", - "task_project_read", - "task_project_write", - "task_task_read", - "task_task_write", - "task_change_read", - "task_comment_read", - "task_comment_write", - "scim_users_read", - "scim_users_write", - "scim_groups_read", - "scim_groups_write", - "lms_course_read", - "lms_course_write", - "lms_class_read", - "lms_class_write", - "lms_student_read", - "lms_student_write", - "lms_instructor_read", - "lms_instructor_write", - "repo_organization_read", - "repo_organization_write", - "repo_repository_read", - "repo_repository_write", - "repo_branch_read", - "repo_branch_write", - "repo_commit_read", - "repo_commit_write", - "repo_pullrequest_read", - "repo_pullrequest_write", - "metadata_metadata_read", - "metadata_metadata_write", - "calendar_calendar_read", - "calendar_calendar_write", - "calendar_event_read", - "calendar_event_write", - "calendar_busy_read", - "calendar_link_read", - "calendar_link_write", - "calendar_recording_read", - "calendar_recording_write", - "enrich_person_read", - "enrich_company_read" -]New value: +[ + "accounting_account_read", + "accounting_account_write", + "accounting_transaction_read", + "accounting_transaction_write", + "accounting_journal_read", + "accounting_journal_write", + "accounting_invoice_read", + "accounting_invoice_write", + "accounting_bill_read", + "accounting_bill_write", + "accounting_creditmemo_read", + "accounting_creditmemo_write", + "accounting_contact_read", + "accounting_contact_write", + "accounting_expense_read", + "accounting_expense_write", + "accounting_taxrate_read", + "accounting_taxrate_write", + "accounting_organization_read", + "accounting_order_read", + "accounting_order_write", + "accounting_purchaseorder_read", + "accounting_purchaseorder_write", + "accounting_salesorder_read", + "accounting_salesorder_write", + "accounting_report_read", + "accounting_report_write", + "accounting_trialbalance_read", + "accounting_trialbalance_write", + "accounting_profitloss_read", + "accounting_profitloss_write", + "accounting_balancesheet_read", + "accounting_balancesheet_write", + "accounting_category_read", + "accounting_category_write", + "payment_payment_read", + "payment_payment_write", + "accounting_cashflow_read", + "accounting_cashflow_write", + "payment_payout_read", + "payment_refund_read", + "payment_link_read", + "payment_link_write", + "payment_subscription_read", + "payment_subscription_write", + "commerce_item_read", + "commerce_item_write", + "commerce_collection_read", + "commerce_collection_write", + "commerce_inventory_read", + "commerce_inventory_write", + "commerce_location_read", + "commerce_location_write", + "commerce_review_read", + "commerce_review_write", + "commerce_saleschannel_read", + "commerce_saleschannel_write", + "commerce_itemvariant_read", + "commerce_itemvariant_write", + "verification_package_read", + "verification_request_read", + "verification_request_write", + "assessment_package_read", + "assessment_package_write", + "assessment_order_write", + "ats_activity_read", + "ats_activity_write", + "ats_application_read", + "ats_application_write", + "ats_applicationstatus_read", + "ats_candidate_read", + "ats_candidate_write", + "ats_interview_read", + "ats_interview_write", + "ats_job_read", + "ats_job_write", + "ats_company_read", + "ats_company_write", + "ats_document_read", + "ats_document_write", + "ats_scorecard_read", + "ats_scorecard_write", + "crm_company_read", + "crm_company_write", + "crm_contact_read", + "crm_contact_write", + "crm_deal_read", + "crm_deal_write", + "crm_event_read", + "crm_event_write", + "crm_lead_read", + "crm_lead_write", + "crm_pipeline_read", + "crm_pipeline_write", + "martech_list_read", + "martech_list_write", + "martech_member_read", + "martech_member_write", + "martech_campaign_read", + "martech_campaign_write", + "martech_report_read", + "martech_report_write", + "ticketing_customer_read", + "ticketing_customer_write", + "ticketing_ticket_read", + "ticketing_ticket_write", + "ticketing_note_read", + "ticketing_note_write", + "ticketing_category_read", + "ticketing_category_write", + "hris_employee_read", + "hris_employee_write", + "hris_group_read", + "hris_group_write", + "hris_payslip_read", + "hris_payslip_write", + "hris_timeoff_read", + "hris_timeoff_write", + "hris_timeshift_read", + "hris_timeshift_write", + "hris_company_read", + "hris_company_write", + "hris_location_read", + "hris_location_write", + "hris_device_read", + "hris_device_write", + "hris_deduction_read", + "hris_deduction_write", + "hris_benefit_read", + "hris_benefit_write", + "hris_bankaccount_read", + "hris_bankaccount_write", + "uc_call_read", + "uc_contact_read", + "uc_contact_write", + "uc_comment_read", + "uc_comment_write", + "uc_recording_read", + "storage_file_read", + "storage_file_write", + "webhook", + "genai_model_read", + "genai_prompt_read", + "genai_prompt_write", + "genai_embedding_read", + "genai_embedding_write", + "messaging_message_read", + "messaging_message_write", + "messaging_channel_read", + "messaging_event_read", + "messaging_event_write", + "kms_space_read", + "kms_space_write", + "kms_page_read", + "kms_page_write", + "kms_comment_read", + "kms_comment_write", + "task_project_read", + "task_project_write", + "task_task_read", + "task_task_write", + "task_change_read", + "task_comment_read", + "task_comment_write", + "scim_users_read", + "scim_users_write", + "scim_groups_read", + "scim_groups_write", + "lms_course_read", + "lms_course_write", + "lms_class_read", + "lms_class_write", + "lms_student_read", + "lms_student_write", + "lms_instructor_read", + "lms_instructor_write", + "lms_content_read", + "lms_content_write", + "lms_collection_read", + "lms_collection_write", + "lms_activity_read", + "lms_activity_write", + "repo_organization_read", + "repo_organization_write", + "repo_repository_read", + "repo_repository_write", + "repo_branch_read", + "repo_branch_write", + "repo_commit_read", + "repo_commit_write", + "repo_pullrequest_read", + "repo_pullrequest_write", + "metadata_metadata_read", + "metadata_metadata_write", + "calendar_calendar_read", + "calendar_calendar_write", + "calendar_event_read", + "calendar_event_write", + "calendar_busy_read", + "calendar_link_read", + "calendar_link_write", + "calendar_recording_read", + "calendar_recording_write", + "calendar_webinar_read", + "calendar_webinar_write", + "enrich_person_read", + "enrich_company_read", + "ads_ad_read", + "ads_ad_write", + "ads_campaign_read", + "ads_campaign_write", + "ads_group_read", + "ads_group_write", + "ads_report_read", + "ads_organization_read", + "ads_organization_write", + "ads_creative_read", + "ads_creative_write", + "ads_insertionorder_read", + "ads_insertionorder_write", + "forms_form_read", + "forms_form_write", + "forms_submission_read", + "forms_submission_write", + "shipping_shipment_read", + "shipping_shipment_write", + "shipping_label_read", + "shipping_label_write", + "shipping_tracking_read", + "shipping_rate_read", + "shipping_carrier_read" +] - added
Input schema / properties / workspace_id / descriptionAdded value: +"(reference to KmsSpace)"
- Changed
update_unified_webhook4 fields changed- changed
Input schema / properties / checked_at / descriptionPrevious value: -"The last date/time that a check was done on this object"New value: +"The last date/time that a check was done on this object (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)" - changed
Input schema / properties / db_type / enumPrevious value: -[ - "mongodb", - "mysql", - "postgres", - "mssql", - "mariadb" -]New value: +[ + "mongodb", + "mysql", + "postgres", + "mssql", + "mariadb", + "supabase" +] - changed
Input schema / properties / object_type / enumPrevious value: -[ - "accounting_account", - "accounting_transaction", - "accounting_journal", - "accounting_contact", - "accounting_invoice", - "accounting_bill", - "accounting_creditmemo", - "accounting_taxrate", - "accounting_organization", - "accounting_order", - "accounting_salesorder", - "accounting_purchaseorder", - "accounting_report", - "accounting_balancesheet", - "accounting_profitloss", - "accounting_trialbalance", - "accounting_category", - "accounting_expense", - "payment_payment", - "payment_link", - "payment_payout", - "payment_refund", - "payment_subscription", - "commerce_item", - "commerce_collection", - "commerce_inventory", - "commerce_location", - "commerce_review", - "verification_package", - "verification_request", - "ats_activity", - "ats_application", - "ats_applicationstatus", - "ats_candidate", - "ats_document", - "ats_interview", - "ats_job", - "ats_scorecard", - "ats_company", - "crm_company", - "crm_contact", - "crm_deal", - "crm_event", - "crm_lead", - "crm_pipeline", - "hris_employee", - "hris_group", - "hris_payslip", - "hris_timeoff", - "hris_company", - "hris_location", - "hris_device", - "hris_timeshift", - "martech_list", - "martech_member", - "passthrough", - "ticketing_note", - "ticketing_ticket", - "ticketing_customer", - "ticketing_category", - "uc_contact", - "uc_call", - "uc_comment", - "uc_recording", - "enrich_person", - "enrich_company", - "storage_file", - "genai_model", - "genai_prompt", - "genai_embedding", - "messaging_message", - "messaging_channel", - "kms_space", - "kms_page", - "kms_comment", - "task_project", - "task_task", - "task_comment", - "task_change", - "scim_users", - "scim_groups", - "lms_course", - "lms_class", - "lms_student", - "lms_instructor", - "repo_organization", - "repo_repository", - "repo_branch", - "repo_commit", - "repo_pullrequest", - "metadata_metadata", - "calendar_calendar", - "calendar_event", - "calendar_busy", - "calendar_link", - "calendar_recording" -]New value: +[ + "accounting_account", + "accounting_transaction", + "accounting_journal", + "accounting_contact", + "accounting_invoice", + "accounting_bill", + "accounting_creditmemo", + "accounting_taxrate", + "accounting_organization", + "accounting_order", + "accounting_salesorder", + "accounting_purchaseorder", + "accounting_report", + "accounting_balancesheet", + "accounting_profitloss", + "accounting_trialbalance", + "accounting_category", + "accounting_expense", + "accounting_cashflow", + "payment_payment", + "payment_link", + "payment_payout", + "payment_refund", + "payment_subscription", + "commerce_item", + "commerce_collection", + "commerce_inventory", + "commerce_location", + "commerce_review", + "commerce_saleschannel", + "commerce_itemvariant", + "verification_package", + "verification_request", + "assessment_package", + "assessment_order", + "ats_activity", + "ats_application", + "ats_applicationstatus", + "ats_candidate", + "ats_document", + "ats_interview", + "ats_job", + "ats_scorecard", + "ats_company", + "crm_company", + "crm_contact", + "crm_deal", + "crm_event", + "crm_lead", + "crm_pipeline", + "hris_employee", + "hris_group", + "hris_payslip", + "hris_timeoff", + "hris_company", + "hris_location", + "hris_device", + "hris_timeshift", + "hris_deduction", + "hris_benefit", + "hris_bankaccount", + "martech_list", + "martech_member", + "martech_campaign", + "martech_report", + "passthrough", + "ticketing_note", + "ticketing_ticket", + "ticketing_customer", + "ticketing_category", + "uc_contact", + "uc_call", + "uc_comment", + "uc_recording", + "enrich_person", + "enrich_company", + "storage_file", + "genai_model", + "genai_prompt", + "genai_embedding", + "messaging_message", + "messaging_channel", + "messaging_event", + "kms_space", + "kms_page", + "kms_comment", + "task_project", + "task_task", + "task_comment", + "task_change", + "scim_users", + "scim_groups", + "lms_course", + "lms_class", + "lms_student", + "lms_instructor", + "lms_content", + "lms_collection", + "lms_activity", + "repo_organization", + "repo_repository", + "repo_branch", + "repo_commit", + "repo_pullrequest", + "metadata_metadata", + "calendar_calendar", + "calendar_event", + "calendar_busy", + "calendar_link", + "calendar_recording", + "calendar_webinar", + "ads_organization", + "ads_ad", + "ads_campaign", + "ads_report", + "ads_group", + "ads_creative", + "ads_insertionorder", + "forms_form", + "forms_submission", + "shipping_carrier", + "shipping_rate", + "shipping_shipment", + "shipping_label", + "shipping_tracking" +] - added
Input schema / properties / workspace_id / descriptionAdded value: +"(reference to KmsSpace)"
- Changed
update_unified_webhook_trigger1 field changed- removed
Input schema / properties / fieldsRemoved value: -{ - "description": "Comma-separated list of fields to include in the response", - "type": "string" -}
16 tool updates
- First observed
create_unified_connection - First observed
create_unified_webhook - First observed
get_unified_apicall - First observed
get_unified_connection - First observed
get_unified_issue - First observed
get_unified_webhook - First observed
list_unified_apicalls - First observed
list_unified_connections - First observed
list_unified_integrations - First observed
list_unified_issues - First observed
list_unified_webhooks - First observed
remove_unified_connection - First observed
remove_unified_webhook - First observed
update_unified_connection - First observed
update_unified_webhook - First observed
update_unified_webhook_trigger
Related MCP Connectors
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceUnified AI Agent SaaS Connector & Multi-Provider Gateway connecting to 1,000+ SaaS platforms, vector databases, and 500+ LLM models via MCP, REST API, and CLI.-
- FlicenseNot gradedqualityCmaintenanceA single MCP server that exposes safe, permission-checked tools for AI assistants to reach file systems, databases, APIs, Git, cloud services, and business applications.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.MIT
- AlicenseNot gradedqualityDmaintenanceUnified MCP server with 46 tools for AI expert consultations, memory service integration (semantic search, knowledge graphs), workflow automation, and code sandboxing.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.