Skip to main content
Glama
getsentry

Sentry MCP

Official
by getsentry

create_team

Add a new team to a Sentry organization by specifying the team name and organization slug, enabling structured collaboration and access management.

Instructions

Create a new team in Sentry.

Use this tool when you need to:

  • Create a new team in a Sentry organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the team to create.
organizationSlugNoThe organization's slug. This will default to the first org you have access to.

Implementation Reference

  • The main execution logic for the create_team tool: authenticates API service, creates team via apiService.createTeam, formats Markdown output with team ID, slug, and name.
    async handler(params, context: ServerContext) {
      const apiService = apiServiceFromContext(context, {
        regionUrl: params.regionUrl ?? undefined,
      });
      const organizationSlug = params.organizationSlug;
    
      setTag("organization.slug", organizationSlug);
    
      const team = await apiService.createTeam({
        organizationSlug,
        name: params.name,
      });
      let output = `# New Team in **${organizationSlug}**\n\n`;
      output += `**ID**: ${team.id}\n`;
      output += `**Slug**: ${team.slug}\n`;
      output += `**Name**: ${team.name}\n`;
      output += "# Using this information\n\n";
      output += `- You should always inform the user of the Team Slug value.\n`;
      return output;
    },
  • Input schema using Zod for validating organizationSlug, optional regionUrl, and required team name.
    inputSchema: {
      organizationSlug: ParamOrganizationSlug,
      regionUrl: ParamRegionUrl.nullable().default(null),
      name: z.string().trim().describe("The name of the team to create."),
    },
  • The create_team tool is registered by exporting the imported createTeam function under the 'create_team' key in the central tools index.
    create_team: createTeam,
  • Import of the create_team implementation module.
    import createTeam from "./create-team";
  • Full tool definition using defineTool, including name registration, description, schema, annotations, and handler.
    export default defineTool({
      name: "create_team",
      requiredSkills: ["project-management"], // Only available in project-management skill
      requiredScopes: ["team:write"],
      description: [
        "Create a new team in Sentry.",
        "",
        "USE THIS TOOL WHEN USERS WANT TO:",
        "- 'Create a new team'",
        "- 'Set up a team called [X]'",
        "- 'I need a team for my project'",
        "",
        "Be careful when using this tool!",
        "",
        "<examples>",
        "### Create a new team",
        "```",
        "create_team(organizationSlug='my-organization', name='the-goats')",
        "```",
        "</examples>",
        "",
        "<hints>",
        "- If any parameter is ambiguous, you should clarify with the user what they meant.",
        "</hints>",
      ].join("\n"),
      inputSchema: {
        organizationSlug: ParamOrganizationSlug,
        regionUrl: ParamRegionUrl.nullable().default(null),
        name: z.string().trim().describe("The name of the team to create."),
      },
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        openWorldHint: true,
      },
      async handler(params, context: ServerContext) {
        const apiService = apiServiceFromContext(context, {
          regionUrl: params.regionUrl ?? undefined,
        });
        const organizationSlug = params.organizationSlug;
    
        setTag("organization.slug", organizationSlug);
    
        const team = await apiService.createTeam({
          organizationSlug,
          name: params.name,
        });
        let output = `# New Team in **${organizationSlug}**\n\n`;
        output += `**ID**: ${team.id}\n`;
        output += `**Slug**: ${team.slug}\n`;
        output += `**Name**: ${team.name}\n`;
        output += "# Using this information\n\n";
        output += `- You should always inform the user of the Team Slug value.\n`;
        return output;
      },
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'creates' a new team. It lacks details on permissions required, whether the operation is idempotent, what happens on duplicate names, or error conditions. For a mutation tool with zero annotation coverage, this is insufficient behavioral disclosure.

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

Conciseness4/5

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

The description is brief and front-loaded with the main purpose, followed by a usage guideline. Both sentences are relevant, though the second sentence could be more efficiently integrated. There's minimal waste, but it's not perfectly structured.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., team ID, success confirmation), error handling, or dependencies like required permissions. For a create operation, this leaves significant gaps for an AI agent.

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 description coverage is 100%, so the schema already documents both parameters ('name' and 'organizationSlug') adequately. The description adds no additional parameter information beyond what's in the schema, meeting the baseline for high coverage but not enhancing understanding.

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 clearly states the action ('Create a new team') and resource ('in Sentry'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_project' beyond mentioning 'team' vs 'project', which is implicit but not explicit about when to choose one over the other.

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

Usage Guidelines3/5

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

The description provides a bullet point stating 'Use this tool when you need to: Create a new team in a Sentry organization', which gives basic context. However, it doesn't specify when NOT to use it or mention alternatives like 'list_teams' for checking existing teams, leaving some ambiguity about usage 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

Related 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/getsentry/sentry-mcp'

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