Skip to main content
Glama

twprojects-create_link

Create a link in a Teamwork project by providing its URL, title, and optional description. Control notifications and tags to keep your team informed.

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 should be notified about the new link. Accepts either 'all' or an object specifying user, team, or company IDs. By default, all project members are notified.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.
Behavior2/5

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

The description does not disclose behavioral traits beyond creation. Annotations are minimal (only a title), so the description carries the full burden. It fails to mention side effects (e.g., notifications sent via 'notify' parameter), authorization requirements, or any constraints that could affect tool behavior.

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

Conciseness2/5

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

The description is extremely terse (two words), which sacrifices completeness. While concise, it omits critical context that could be included without verbosity. A more structured description (e.g., 'Creates a new link in a project with optional tags and notifications') would maintain brevity while improving clarity.

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

Completeness2/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 minimal annotations, the description is incomplete. It does not explain what happens on success (e.g., returns the created link), error conditions (e.g., invalid project_id), or how the tool integrates with related entities (e.g., tags, notifications). The schema provides parameter details but the description lacks operational context.

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?

The input schema has 100% coverage with detailed descriptions for each parameter, including optional notify object structure and required fields. The description 'Create link' adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema already provides sufficient parameter semantics.

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?

The description 'Create link' clearly identifies the verb (create) and resource (link), making its purpose immediately understandable. However, it does not differentiate from sibling tools like twprojects-create_task or twprojects-create_comment, lacking specificity about what a 'link' represents in this context.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives (e.g., twprojects-update_link for modifications) or any prerequisites (e.g., must have project_id). This leaves the agent without guidance on appropriate invocation scenarios.

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