Google Address Validation MCP integration for AI agents.
Connect AI agents to Google Address Validation through 2 structured actions, including provide validation feedback and validate address. Review authenticatio…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Google Address Validation integration exposes
The Google Address Validation Agent App exposes 2 provider-backed actions for location and data work. Its current contract lets an authorized agent send the final outcome of a completed google address validation sequence using the first responseid from that sequence and validate and standardize a postal address with google address validation and return verdict, parsed address, and geocode details. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Google Address Validation account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Google Address Validation capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
provide_validation_feedbackREVIEWSend the final outcome of a completed Google address validation sequence using the first responseId from that sequence.
INPUTS: responseId / conclusion
validate_addressREVIEWValidate and standardize a postal address with Google Address Validation and return verdict, parsed address, and geocode details.
INPUTS: address / previousResponseId / sessionToken / enableUspsCass / languageOptions
INPUT CONTRACTS
Know what the action needs before it runs.
provide_validation_feedback
responseIdOPTIONAL- The first responseId from the validation sequence.
conclusionOPTIONAL- Outcome of the completed address validation sequence.
validate_address
addressREQUIRED- Structured postal address input accepted by Google Address Validation.
previousResponseIdOPTIONAL- The first responseId from the validation sequence for follow-up requests.
sessionTokenOPTIONAL- Optional Places Autocomplete session token for billing and workflow linking.
enableUspsCassOPTIONAL- Whether to enable USPS CASS mode for US and PR addresses.
languageOptionsOPTIONAL- Optional Google Address Validation language options.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Provide Validation Feedback
Send the final outcome of a completed Google address validation sequence using the first responseId from that sequence. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
provide_validation_feedbackVerify with Validate Address
Validate and standardize a postal address with Google Address Validation and return verdict, parsed address, and geocode details. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
validate_addressSAFETY BOUNDARY
Operate Google Address Validation with explicit limits
- Authorize Google Address Validation with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Google Address Validation data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Google Address Validation rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Google Address Validation task completed successfully.
CONNECTION MODEL
API key
Google Maps Platform API key used with the Address Validation API. Create or manage it in the Google Cloud Console: https://developers.google.com/maps/documentation/address-validation/use-address-validation-api
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Google Address Validation.