Skip to main content
Glama

notify_team_members

Notify workspace team members about a newly created or updated resource, respecting their notification preferences and Do Not Disturb settings.

Instructions

Notify all eligible workspace team members about a resource you just created or updated — file, workflow, agent, or library. Use this when the user says things like "notify the team of this new file", "let everyone know about this workflow", or "notify @sarah about this". Respects each member's notification preferences and Do Not Disturb settings. Returns how many members were notified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNoOptional additional context to include in the notification
memberIdsNoOptional list of member UUIDs to notify. Use memberNames or memberEmails instead when possible.
resourceIdYesThe UUID of the resource
memberNamesNoOptional list of member display names to notify (case-insensitive). Prefer this when the user says things like "notify Sarah" or "notify Tom and Alice".
workspaceIdNoWorkspace ID (uses default if omitted)
memberEmailsNoOptional list of member email addresses to notify.
resourceNameYesHuman-readable name of the resource, used in the notification text
resourceTypeYesThe type of resource being shared
notificationTypeNoNotification preference type. Defaults to "newFileCreated". Use "mention" when notifying a specific person.
Behavior4/5

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

No annotations provided, but description discloses key behaviors: respects notification preferences and Do Not Disturb, returns count of notified members. Could add more on constraints (e.g., resource must be recently created/updated) but sufficient.

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 concise sentences with no redundancy; purpose and usage are front-loaded. Every sentence adds necessary information.

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?

Given 9 parameters and no output schema, the description covers purpose, usage, behavioral traits, and return. Lacks details on permissions/ownership prerequisites but otherwise complete.

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% with parameter descriptions. Description adds value by advising preference for memberNames over memberIds for user queries, but does not significantly enrich meaning beyond schema.

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

Purpose5/5

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

Description clearly states the tool notifies team members about a resource, listing specific resource types (file, workflow, agent, library) and example user phrases, distinguishing it from sibling tools like share_create or add_comment.

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?

Provides explicit usage triggers with example user queries, but lacks explicit when-not-to-use guidance or alternative tool comparisons. Still clear for agents.

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/contextium-io/contextium-mcp-server'

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