Skip to main content
Glama
TylerIlunga

Procore MCP Server

Grant App Authorization

grant_app_authorization
Read-onlyIdempotent

Generate a temporary OAuth 2.0 authorization code to grant an application access to Procore.

Instructions

Creates and returns a temporary authorization code with 10 minute expiration. Note that all parameters listed below are required. This endpoint corresponds to the OAuth 2.0 authorization endpoint described in section 3.1 of the OAuth 2.0 RFC. See the Authentication Guide for additional information and authentication examples. Use this to read information about Authentication records from Procore. Returns a paginated JSON array of Authentication records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: response_type, client_id, redirect_uri. Procore API: Platform - Developer Tools > Authentication. Endpoint: GET /oauth/authorize

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_typeYesQuery string parameter — response type. Value should be `code` for server apps, `token` for client apps.
client_idYesQuery string parameter — client ID you were assigned when you registered your application.
redirect_uriYesQuery string parameter — the URI that the user will be redirected to after they grant authorization to your application. For browser-based web applications, use a `https://` web address. For "headless" applications use `ur...
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior1/5

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

Description contradicts annotations: annotations set readOnlyHint=true and destructiveHint=false (indicating a read-only operation), but description states it 'creates and returns a temporary authorization code', implying a write. This is a flagrant annotation contradiction.

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 verbose and contains contradictory, irrelevant statements (e.g., 'Returns a paginated JSON array...' which conflicts with earlier purpose). Not concise, and key information is buried.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's critical role (OAuth authorization), the description is severely incomplete and contradictory. It fails to clarify the tool's actual behavior, making it nearly impossible for an agent to use correctly.

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%, so the schema already documents all parameters thoroughly. The description adds no additional semantic value beyond stating required parameters, which is already in schema. Baseline score of 3 is appropriate.

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

Purpose1/5

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

The description contradicts itself: first claims to create an authorization code (write), then says it reads Authentication records. This makes the actual purpose unclear and misleading.

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

Usage Guidelines1/5

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

No guidance on when to use this tool vs alternatives. The description references OAuth 2.0 but fails to clarify when to use grant_app_authorization over other authentication-related endpoints. The conflicting statements add confusion.

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/TylerIlunga/procore-mcp-server'

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