Skip to main content
Glama
Upload-Post

Upload-Post

Official

Get team info

get_team_info
Read-only

Retrieve read-only team details such as role permissions, member status, shared account access, and audit activity to support collaboration and approval management.

Instructions

Read-only team data. roles: the role matrix (owner, admin, editor, contributor, viewer and what each can do), whether roles and approvals are enabled, and the caller's own role and profiles. members: the owner's team members with status and, with roles on, role and profiles (null = every profile); not available to members. shared_with_me: accounts whose team the caller belongs to, with the caller's role there. audit: what members did (post_created, published, scheduled_edited, scheduled_cancelled, approval_requested, draft_created, approval_edited, approved, rejected, approval_withdrawn, approval_expired, member_access_changed), newest first, owner and Admin only; filters actor, action, profile_username, target_id, since, until (ISO 8601), limit (1-200), cursor (= next_cursor). Roles and member access are changed by the account owner in the dashboard.

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": {
      "action": "<action>"
    },
    "name": "get_team_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoaudit: only this member email.
limitNoaudit: rows per page, 1-200. Default 50.
sinceNoaudit: ISO 8601, inclusive.
untilNoaudit: ISO 8601, exclusive.
actionYes
cursorNoaudit: `next_cursor` of the previous page.
target_idNoaudit: only this approval or job id.
audit_actionNoaudit: only this kind of activity.
profile_usernameNoaudit: only this profile.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: per-action authorization tiers and the dashboard redirect for writes. It does not, however, say what happens on an unauthorized call (empty result vs. error) or address pagination behavior beyond the cursor field, so the addition is moderate rather than rich.

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?

Nearly every clause carries non-redundant information and the read-only/safety framing is front-loaded, so it is efficiently sized for a four-mode tool. The execution is a single dense run-on paragraph of semicolon-separated fragments, though, which makes the per-action permission and parameter rules harder to scan than a short bulleted breakdown would be.

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?

With a rich annotation set, an output schema that covers return values, and high schema description coverage, the description's remaining job is scope and authorization, and it delivers both per action. The only meaningful gap is failure behavior under insufficient permissions, which matters because two of the four modes are explicitly gated.

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 89%, so the baseline is 3 and the description mostly restates it (the audit filter names, the ISO 8601 formats, limit 1-200, "cursor (= next_cursor)" all mirror schema text). It does add the scoping rule that every filter is audit-only and that profiles is "null = every profile", but it also introduces a real ambiguity: the filter list says "action" while the actual property is `audit_action`, which collides in name with the required top-level `action` selector and could lead an agent to misuse it.

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?

Opens with a specific verb+resource ("Read-only team data") and then enumerates the four action modes with the exact payload each returns (role matrix, member list, accounts the caller belongs to, audit events). An agent knows precisely what the tool surfaces, and no sibling in the catalog overlaps with team/role/member data, so explicit differentiation isn't needed. It loses a point only because the top-line purpose sentence is terse and the real specification is buried in the colon-delimited enumeration.

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 real selection conditions per mode: "members" is "not available to members", and "audit" is "owner and Admin only", which lets an agent rule modes in or out before calling. It also closes the mutation loop by stating "Roles and member access are changed by the account owner in the dashboard", i.e. this tool is not the write path. It stops short of naming any alternative tool or describing what to do on a permission denial.

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

Deploy Server

Other Tools