Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Or Refresh An Access Token

get_or_refresh_an_access_token

Acquire a new access token or refresh an existing one for Procore API authentication using OAuth 2.0. Required parameters: grant_type, client_id, client_secret.

Instructions

Used to acquire a new access token or refresh an existing access token. Certain parameter combinations and values are used depending on which scenario you are handling. See the individual parameter descriptions for additional information. This endpoint corresponds to the token endpoint described in section 3.2 of the OAuth 2.0 RFC. See the Authentication Guide for additional information and authentication examples. JavaScript applications cannot make this ... Use this to perform the get or action on Authentication records. Creates a new Authentication records and returns the created object on success (HTTP 201). Required parameters: grant_type, client_id, client_secret. Procore API: Platform - Developer Tools > Authentication. Endpoint: POST /oauth/token

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grant_typeYesJSON request body field — use the value `authorization_code` when getting a new access token. Use `refresh_token` when refreshing an existing access token. Use `client_credentials` when using a Procore Service Account for a...
client_idYesJSON request body field — client ID you were assigned when you registered your application.
client_secretYesJSON request body field — client Secret you were assigned when you registered your application.
codeNoJSON request body field — value of the `authorization_code` retrieved from the `/oauth/authorize` call. Only required when getting a new access code.
redirect_uriNoJSON request body field — 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...
refresh_tokenNoJSON request body field — the refresh token string. Only required when refreshing an access token.
Behavior4/5

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

Annotations indicate this is not read-only (readOnlyHint=false), and the description confirms it creates a new Authentication record on success, which is a write operation. It also references the OAuth 2.0 RFC for standard behavior. No contradictory statements. It adds useful behavioral context beyond annotations.

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

Conciseness3/5

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

The description front-loads the core purpose but includes redundant sentences and a truncated line ('JavaScript applications cannot make this ...'), which detracts from conciseness. It could be tightened.

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

Completeness3/5

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

Given the complexity of OAuth token flows, the description includes an endpoint reference, OAuth RFC citation, and a link to the authentication guide. However, it lacks details about the response format (e.g., token expiry, refresh token), and there is no output schema to compensate.

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?

The input schema has 100% description coverage, so the schema itself documents each parameter's meaning. The tool description adds no additional semantic detail beyond the schema, merely advising to 'see the individual parameter descriptions.' Baseline of 3 is appropriate.

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 tool's purpose: acquiring or refreshing an access token. It identifies the specific verb-resource combination. However, it contains redundant and somewhat confusing phrases like 'perform the get or action on Authentication records' and 'Creates a new Authentication records' which slightly obscure clarity.

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 mentions that different parameter combinations apply to different scenarios (getting vs. refreshing) and refers to the parameter descriptions. It provides a link to an authentication guide. However, it does not explicitly state when not to use this tool or contrast it with alternative tools, which are numerous in the sibling list.

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