Skip to main content
Glama

twprojects-create_link

Create a link in a Teamwork project by specifying its URL and optional title, description, tags, and notification settings.

Instructions

Create link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe URL of the link. This is the actual web address that the link points to.
descriptionNoThe description of the link. Longer text that provides detailed information about the link.
notifyNoWho to notify of the new link.all
notify_current_userNoWhether the current user should be notified about the new link.
project_idYesThe ID of the project to create the link in.
tag_idsNoA list of tag IDs to associate with the link.
titleNoThe title of the link, which provides a brief summary of the purpose of the link.
Behavior1/5

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

The description lacks any behavioral details beyond the bare action. Annotations provide no hints (no readOnlyHint, destructiveHint). The description does not mention authentication, idempotency, side effects, or permissions. For a mutation tool, this is critically insufficient.

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

Conciseness1/5

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

The description is extremely concise (three words) but under-specified. It does not front-load key information; it is essentially a placeholder. Conciseness should save words without sacrificing clarity, which is not achieved here.

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

Completeness1/5

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

Given the tool has 7 parameters, no output schema, and no annotations, the description must provide significant context. It provides none. Missing details include return value, error states, and behavior when required parameters are missing.

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% and the schema includes good descriptions for each parameter (e.g., 'code' as URL, 'title' as brief summary). The description adds nothing beyond the schema, meriting the baseline score of 3.

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

Purpose2/5

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

The description 'Create link.' is a tautology of the tool name and title. It does not specify what kind of link (e.g., URL link in a project) or distinguish from other create tools. The input schema reveals it creates a project link with a URL, but the description fails to convey this.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus other creation tools (e.g., twprojects-create_file, twprojects-create_task). There is no context about prerequisites or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Teamwork/mcp'

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