Skip to main content
Glama
MSPbotsAI

openai-workspace-mcp

by MSPbotsAI

openai_list_audit_logs

List user actions and configuration changes in your OpenAI organization, filtering by time, actor, event type, project, or resource to monitor activity and enhance security.

Instructions

List user actions and configuration changes in the organization.

    Args:
        effective_start_time: Only events at/after this Unix timestamp (seconds).
        effective_end_time: Only events before this Unix timestamp (seconds).
        actor_emails: Only events performed by users with these emails.
        actor_ids: Only events performed by these actors (user, service
            account, or API key tracking IDs).
        event_types: Only events of these types, e.g. `project.created`,
            `user.added`, `api_key.deleted`, `invite.sent`. See
            https://platform.openai.com/docs/api-reference/audit-logs/object
            for the full enum.
        project_ids: Only events scoped to these projects.
        resource_ids: Only events affecting these resource IDs.
        after: Pagination cursor from a previous response's `last_id`.
        before: Pagination cursor to fetch the previous page.
        limit: Maximum number of events to return per page.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
actor_idsNo
event_typesNo
project_idsNo
actor_emailsNo
resource_idsNo
effective_end_timeNo
effective_start_timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description must convey behavioral traits on its own. It implies a read-only operation via the verb 'List' and details pagination parameters, but it does not explicitly state permission requirements, retention limits, or the lack of side effects. This is moderate transparency.

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?

The description is front-loaded with a clear purpose statement, followed by a structured list of arguments. Each sentence is informative and necessary for a 10-parameter tool, with no filler or redundancy.

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?

The description fully explains the purpose and all parameters, and the presence of an output schema covers return values. However, it omits explicit usage context such as authentication requirements or typical scenarios, leaving some gaps for a tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero property descriptions, so the documentation of all 10 parameters in the description is essential. Each parameter is explained with meaningful context (e.g., time formats, actor types, event type examples), fully compensating for the missing schema descriptions.

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?

The description clearly states 'List user actions and configuration changes in the organization,' which uses a specific verb and resource. This distinguishes it from sibling tools that manage projects, invites, users, API keys, and other resources, so there is no ambiguity.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It only lists parameters without any mention of use cases, prerequisites, or situations where another tool would be more appropriate, leaving the agent to infer usage.

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/MSPbotsAI/openai-workspace-mcp-'

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