Dutify

pm_configure_task_sharing

Destructive

Enable, disable, or reconfigure public sharing for a task. Pass shared: true to generate a public link (or refresh the configuration); the response includes the resulting publicLink. Pass shared: false to revoke an existing share. All other fields are optional toggles for which slices of the task are visible to a public viewer. Requires FULL access to the task. API-key scope: tasks:write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskIdentifier": "<taskIdentifier>"
    },
    "name": "pm_configure_task_sharing"
  }
}

Input Schema

Name	Required	Description
`shared`	No	true to publish, false to revoke
`account`	No	Multi-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
`expiresAt`	No	Optional ISO 8601 timestamp when the share link should auto-expire (e.g. "2026-12-31T23:59:59Z")
`shareTags`	No	Expose tags
`workspace`	No	Workspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.
`shareStatus`	No	Expose current status
`shareDueDate`	No	Expose due date
`shareAssignee`	No	Expose assignees on the public view
`shareComments`	No	Expose comments
`sharePriority`	No	Expose priority
`shareSubtasks`	No	Expose subtasks
`taskIdentifier`	Yes	Task identifier (tsk_…) or short key
`shareAttachments`	No	Expose file attachments
`shareDescription`	No	Expose task description
`shareCustomFields`	No	Expose custom field values
`sharedCustomFieldIdentifiers`	No	Explicit allow-list of custom-field identifiers to expose (when shareCustomFields=true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real context beyond the annotations: the response carries a publicLink, publishing refreshes an existing configuration, and FULL task access plus tasks:write scope are required. What is not disclosed is the blast radius of a reconfigure (whether toggling fields silently hides content from already-issued links) or whether revoking invalidates prior URLs.

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

Conciseness5/5

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

Four sentences, front-loaded with the action, then the true/false semantics, then the toggle meaning, then the access requirement. Nothing repeated and nothing padding.

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

Completeness4/5

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

Covers the essentials for a 16-parameter mutation with no output schema: action, mode semantics, auth requirement, and the notable return field. Gaps are around edge behavior (reconfiguring an existing share, interaction between custom-field flags) rather than core invocation.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description explains the shared flag's two modes and frames the remaining booleans as 'which slices of the task are visible to a public viewer', but it does not clarify the interaction between shareCustomFields and sharedCustomFieldIdentifiers or the expiresAt behavior beyond what the schema already says.

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

Purpose4/5

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

States a specific verb set ('Enable, disable, or reconfigure') against a specific resource ('public sharing for a task'), so the mutation role is unmistakable. It doesn't name or contrast with the read-side sibling pm_get_task_sharing, leaving that routing to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditions for the two modes ('shared: true' to publish or refresh, 'shared: false' to revoke) plus prerequisites ('Requires FULL access to the task', 'API-key scope: tasks:write'). No explicit when-not guidance or reference to pm_get_task_sharing as the read alternative.

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

All Dutify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?